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.

Sign up for GitHub

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

Jump to bottom

Merging complex objects / types (geo, objects) can cause failure to lookup field names (without type prefix) #1016

Closed
tozz opened this issue Jun 10, 2011 · 1 comment
Closed

Merging complex objects / types (geo, objects) can cause failure to lookup field names (without type prefix) #1016

tozz opened this issue Jun 10, 2011 · 1 comment
Labels
>bug v0.16.3 v0.17.0

Comments

@tozz
Copy link

tozz commented Jun 10, 2011

When specifying a geo_point type in 16.2 geo_distance facet fails. Example works in 16.1 and 16.0
Error: FacetPhaseExecutionException[Facet [geotest]: No mapping found for field [locations]]

Curl recreation at https://gist.github.com/2ba2e3d0d50a5e4c777c
The empty document does throw an error but the bug is reproducible even with a non-empty document.
@kimchy
Copy link
Member

kimchy commented Jun 10, 2011

I see where the problem is, I will change the title a bit and push a fix soon.

@kimchy kimchy closed this as completed in eca2440 Jun 10, 2011
hibnico pushed a commit to hibnico/elasticsearch that referenced this issue Jun 27, 2011
@kimchy
Merging complex objects / types (geo, objects) can cause failure to l…
d9e85ea 
…ookup field names (without type prefix), closes elastic#1016.
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
Merging complex objects / types (geo, objects) can cause failure to l…
7206b2b 
…ookup field names (without type prefix), closes elastic#1016.
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
@Gschiavon @jbaiera
Fixed reference to maven dependency in README (elastic#1016)
5059c28
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
@kares
Docs: mention synthetics being supported (elastic#1016)
2f8ebf0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.16.3 v0.17.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @tozz