-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Comments
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. |
This may be useful in designing an api for spatial search: http://geojson.org/geojson-spec.html |
Interesting. I will certainly have a look at this once I tackle local lucene. |
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? |
The features we were looking for were: 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) |
cool, I will close this issue. It would be a great help if you can take this features for a test drive. |
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
Adding the ability to do geospatial indexing/searching using local lucene would be very useful, and a good candidate for a plugin.
The text was updated successfully, but these errors were encountered: