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

Geoshape filter can't handle multiple shapes #3242

Closed
chilling opened this Issue Jun 26, 2013 · 5 comments

Comments

Projects
None yet
3 participants
@chilling
Copy link
Contributor

chilling commented Jun 26, 2013

The geo_shape filter seems to be unable to handle multiple geo_shape fields in a single document if this document is used as indexed filter.

Assume a mapping with multiple geo_shape fields:

{
    "type1" : {
        "properties" : {
            "location1" : {
                 "type" : "geo_shape"
            },
            "location2" : {
                "type" : "geo_shape"
            }
        }
    }
}

and a document

{
    "location1" : {
        "type":"polygon",
        "coordinates":[[[-10,-10],[10,-10],[10,10],[-10,10],[-10,-10]]]
    },
    "location2" : {
        "type":"polygon",
        "coordinates":[[[-20,-20],[20,-20],[20,20],[-20,20],[-20,-20]]]
    }
}

If a geo_shape filter is applied to the location2 field

{
    "geo_shape": {
        "location2": {
            "indexed_shape": { 
                "id": "1",
                "type": "type1",
                "index": "test",
                "shape_field_name": "location2"
            }
        }
    }
}

parsing fails with

ElasticSearchIllegalStateException[Shape with name [1] found but missing location2 field];
@alexeiemam

This comment has been minimized.

Copy link

alexeiemam commented Sep 7, 2013

Is this fix included in the 0.90.3 release?
I am currently experiencing the same error when both a geo_shape and a geo_point field are present in the same document.

Edit: using 0.90.3

@s1monw

This comment has been minimized.

Copy link
Contributor

s1monw commented Sep 7, 2013

this has never been backported... I will backport!

@s1monw s1monw reopened this Sep 7, 2013

chilling added a commit that referenced this issue Sep 7, 2013

@s1monw

This comment has been minimized.

Copy link
Contributor

s1monw commented Sep 7, 2013

pushed to 0.90 branch. This will be part of 0.90.4

@s1monw s1monw closed this Sep 7, 2013

@alexeiemam

This comment has been minimized.

Copy link

alexeiemam commented Sep 8, 2013

When is the, approximate, anticipated release of 0.90.4?

@s1monw

This comment has been minimized.

Copy link
Contributor

s1monw commented Sep 8, 2013

When is the, approximate, anticipated release of 0.90.4?

we plan on a release early next week

@chilling chilling removed their assignment Mar 10, 2015

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.