Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

locallucene plugin #100

Closed
grantr opened this issue Mar 31, 2010 · 6 comments
Closed

locallucene plugin #100

grantr opened this issue Mar 31, 2010 · 6 comments

Comments

@grantr
Copy link

grantr commented Mar 31, 2010

Adding the ability to do geospatial indexing/searching using local lucene would be very useful, and a good candidate for a plugin.

@kimchy
Copy link
Member

kimchy commented Mar 31, 2010

Agreed, spatial search is something that I am going to work on. I don't even think it will be a plugin, but a core feature (attachments would have been core as well if it wasn't so big in terms of size).

Regarding the implementation itself, it seems like the spatial package is going through a lot of changes, so it will be delicate to create something that will survive the changes.

@grantr
Copy link
Author

grantr commented May 19, 2010

This may be useful in designing an api for spatial search: http://geojson.org/geojson-spec.html

@kimchy
Copy link
Member

kimchy commented May 19, 2010

Interesting. I will certainly have a look at this once I tackle local lucene.

@kimchy
Copy link
Member

kimchy commented Aug 8, 2010

Have been doing a lot of geo related work for the upcoming 0.9.1. Can you take a look and see if there is something missing? In any case, if there is, it would be great to raise it in the mailing list or another issue so we focus on specific features. What do you think, can this issue be closed?

@grantr
Copy link
Author

grantr commented Aug 9, 2010

The features we were looking for were:
radius (distance from point) search
bounding box search
polygon search
sort by distance from point

It looks like all of these have been implemented in 0.9.1 (I've been following commits closely). So I think this issue can safely be closed.

This is a really big deal for us! It finally allows us to drop sphinx for elasticsearch (sphinx supports geo distance sort), and we can add features that we couldn't with sphinx (thanks to polygon search)

@kimchy
Copy link
Member

kimchy commented Aug 9, 2010

cool, I will close this issue. It would be a great help if you can take this features for a test drive.

cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
During the cut-over period Jenkins jobs get started at the same time
for the old and new env potentially having the same trial-timestamp.
This results in failure to copy results[1] as they may include docs from
a different env.

Additionally there's a risk of copying over results related to another race config
if both run on the same environment at the same time (same effective date).

Fix issue, by populating user-tag.race-configs-id also for nightlies and
additionally filtering by environment name and race-configs-id.

[1] https://elasticsearch-ci.elastic.co/view/All/job/elastic+elasticsearch+master+macrobenchmark-periodic-group-1/2/console

Relates elastic#100
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants