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
Geo: Polygon based filter #294
Comments
Geo: Polygon based filter, closed by 959eb0e. |
What is that "drn5x1g8cu2y" in the last example? Thanks. |
Thats a geohash. |
I am having a problem getting the geo location stuff to work with v0.15 on windows 7 x64. Sun JDK 1.6.0.20. I have done many things successfully with elasticsearch but just struggling with this. Also why is pin.location required, i.e. why is pin outer required? I was following examples. Remember on windows need to use " instead of '. The " need to be repeated 3 times to escape. The following command returns success... \gnu\bin\curl\curl -XPUT "http://localhost:9200/scratch/test/12345" -d "{"""pin""":{"""MyId""":12345,"""location""":{"""type""":"""geo_point""","""lat""":40.12,"""lon""":-71.34}}}" The following errors \gnu\bin\curl\curl -XGET "http://localhost:9200/scratch/test/_search?pretty=true" -d "{"""filtered""":{"""query""":{"""match_all""":{}},"""filter""":{"""geo_polygon""":{"""pin.location""":{"""points""":[{"""lat""":40,"""lon""":-70},{"""lat""":30,"""lon""":-80},{"""lat""":20,"""lon""":-90}]}}}}}" { [2011-03-05 13:04:26,294][DEBUG][action.search.type ] [Stonecutter] [scratch][4], node[AlmTJezeRUir7yIqVQ5cWA], [P], s[STARTED |
Can you create a recreation and gist it, and then post it on the mailing list? (check http://www.elasticsearch.org/help). |
Got it working eventually. Unfortunately the examples were not clear / misleading / being new to elasticsearch. We found a subsequent comment somewhere which mentioned that geo_point no longer automatically detected. I manually defined the index and specified type as geo_point. Extra " because via windows command line... {"""location""":{"type":"""geo_point"""}} I didn't wrap with outer "pin". I then imported data. We then had to wrap the "filtered" with a "query":{ } which is not shown in examples. Here is example of query for windows command line which returns matches for UK and Ireland... \curl -XGET "http://localhost:9200/scratch/test/_search?pretty=true" -d "{"""query""":{"""filtered""":{"""query""":{"""match_all""":{}},"""filter""":{"""geo_bounding_box""":{"""location""":{"""top_left""":{"""lat""":60,"""lon""":-10},"""bottom_right""":{"""lat""":50,"""lon""":-0}}}}}}}" Useful website for working out long and lats. |
Great. In the geo polygon filter it states that the geo_type is required: http://www.elasticsearch.org/guide/reference/query-dsl/geo-polygon-filter.html. |
Thanks. As a newbie to elasticsearch I wasn't clear what this meant. I tried passing as part of query explicitly. If examples were a little more complete and included actual curl command would greatly assist for novices. ElasticSearch is looking very promising! |
Since in many cases Pig internal assumptions force the use of 1 reducer, no matter the job properties or the number of splits, document the settings that disable this behavior (and which unfortunately cannot be set directly by es-hadoop). fix elastic#294
…ull request elastic#294) Initial support for ARM based EMS EC2 instances Add support for c6g type instances so we could start validating AWS claims for better price performance (allegedly 40%): * Added "--arch" build flag. * EMS AMI names include architecture: packer-ems-<amd64|arm64>-<version>-<date>-<time> * Terraform infers the architecture based on the instance family - it it ends with "g" it will look for arm64 AMIs. * Updated provisioner scripts that assumed amd64 architecture. In some cases, took a shortcut for now: dequeue does not support ARM because of lack of chrome builds, temporarily skipping cloud watch agent. * Also: delete_ami.py can delete multiple AMI IDs Approved-by: fabien
Rearrange some classes into the process Introduce small additional infra classes such as FilterExec
A filter allowing to include hits that only fall within a polygon of points. Here is an example:
Other formats supported:
and,
and
The text was updated successfully, but these errors were encountered: