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

Any plans to add geospatial search? #4

Closed
simonw opened this Issue Feb 11, 2010 · 3 comments

Comments

Projects
None yet
2 participants
@simonw
Contributor

simonw commented Feb 11, 2010

It would be incredibly useful to be able to index documents with latitude/longitude positions and run searches that return results ordered by distance from a specific latitude/longitude point.

@kimchy

This comment has been minimized.

Member

kimchy commented Feb 11, 2010

Yes, very much. There is a Lucene spatial module that I need to look at. There are other solutions running around. When I support that, I want that to be very closely integrated in terms that you will have a type: location (or something similar).

Not sure it will make it into 0.5, but its certainly on the short list for 0.6.0.

@simonw

This comment has been minimized.

Contributor

simonw commented Feb 11, 2010

Thanks - it's a very exciting project, thanks for releasing it!

@kimchy

This comment has been minimized.

Member

kimchy commented Feb 12, 2010

I will close this for now, I will add an issue that says "Spatial Support" later on

dadoonet added a commit that referenced this issue Jun 5, 2015

Move to Elasticsearch 0.21.0.Beta1
Due to refactoring in 0.21.x we have to update this plugin
Closes #4.

dadoonet added a commit that referenced this issue Jun 5, 2015

dadoonet added a commit that referenced this issue Jun 5, 2015

Moving log level to debug
We don't want to have too much INFO log level. So we move some parts to log.debug.

Closes #4.

dadoonet added a commit that referenced this issue Jun 5, 2015

dadoonet added a commit that referenced this issue Jun 5, 2015

dadoonet added a commit that referenced this issue Jun 9, 2015

rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015

rahul1193 referenced this issue in rahul1193/elasticsearch Jan 9, 2017

jasontedor added a commit to jasontedor/elasticsearch that referenced this issue Jan 31, 2018

Allow whitelist of packages that can exit
Today, SecureSM has a mechanism that enables a hardcoded list of test
packages to exit if the SecureSM instance is constructed with a boolean
flag indicating that these packages will be permitted to exit. This
commit replaces this mechanism by allowing the SecureSM instance to be
constructed with a whitelist of packages that can exit.

Relates elastic#4

jasontedor added a commit that referenced this issue Jan 31, 2018

Allow whitelist of packages that can exit
Today, SecureSM has a mechanism that enables a hardcoded list of test
packages to exit if the SecureSM instance is constructed with a boolean
flag indicating that these packages will be permitted to exit. This
commit replaces this mechanism by allowing the SecureSM instance to be
constructed with a whitelist of packages that can exit.

Relates #4

vladimirdolzhenko added a commit to vladimirdolzhenko/elasticsearch that referenced this issue May 4, 2018

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment