}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:
398)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:
311)
at
org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:
162)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteQuery(SearchServiceTransportAction.java:
131)
at
org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction
$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryThenFetchAction.java:
77)
at org.elasticsearch.action.search.type.TransportSearchTypeAction
$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:195)
at org.elasticsearch.action.search.type.TransportSearchTypeAction
$BaseAsyncAction.access$000(TransportSearchTypeAction.java:81)
at org.elasticsearch.action.search.type.TransportSearchTypeAction
$BaseAsyncAction$1.run(TransportSearchTypeAction.java:154)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
Caused by: org.elasticsearch.index.query.QueryParsingException:
[places_2010100101] No query parser registered for [null]
at
org.elasticsearch.index.query.xcontent.QueryParseContext.parseInnerFilter(QueryParseContext.java:
168)
at
org.elasticsearch.index.query.xcontent.OrFilterParser.parse(OrFilterParser.java:
64)
at
org.elasticsearch.index.query.xcontent.QueryParseContext.parseInnerFilter(QueryParseContext.java:
170)
at
org.elasticsearch.index.query.xcontent.FilteredQueryParser.parse(FilteredQueryParser.java:
67)
at
org.elasticsearch.index.query.xcontent.QueryParseContext.parseInnerQuery(QueryParseContext.java:
144)
at
org.elasticsearch.index.query.xcontent.XContentIndexQueryParser.parse(XContentIndexQueryParser.java:
234)
at
org.elasticsearch.index.query.xcontent.XContentIndexQueryParser.parse(XContentIndexQueryParser.java:
214)
at
org.elasticsearch.search.query.QueryParseElement.parse(QueryParseElement.java:
34)
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:
385)
... 10 more
I'm trying to use the new named filters feature in 0.11 and getting a
QueryParsingException on this query:
I haven't tried these yet, but looking at the issuehttp://github.com/elasticsearch/elasticsearch/issues/issue/364
it seems that you should put the "_name" inside the filter:
It seems that without the _name fields in the filters, the query runs
in < 0.01s, while with them it runs in about 2s. A drastic difference.
I only have about 120 documents in the index. Is there an explanation
for this?
There should not be that big different, can you post a test that fills
elasticsearch with data and recreates it? Note that the first time executing
it might take time, second executions should be faster.
It seems that without the _name fields in the filters, the query runs
in < 0.01s, while with them it runs in about 2s. A drastic difference.
I only have about 120 documents in the index. Is there an explanation
for this?
By first time, I meant first time something "touches" the lat/lon values, it
will cause them to be loaded, and then executions on them will be fast. Post
that, same filter execution will also be faster because filter results are
further cached.
There should not be that big different, can you post a test that fills
elasticsearch with data and recreates it? Note that the first time executing
it might take time, second executions should be faster.
It seems that without the _name fields in the filters, the query runs
in < 0.01s, while with them it runs in about 2s. A drastic difference.
I only have about 120 documents in the index. Is there an explanation
for this?
I posted the test file that contains a sequence of curl commands that
creates and populates the index and does the search with and without
named filters.
There should not be that big different, can you post a test that fills
elasticsearch with data and recreates it? Note that the first time executing
it might take time, second executions should be faster.
I am trying to see if its possible to support this expected behavior from
curl, but the http lib I use does not have a nice extension point for
handling it, so working on a patch for them. In any case, that extra
chitchat is better disabled even if there is support for this curl
behavior.
I posted the test file that contains a sequence of curl commands that
creates and populates the index and does the search with and without
named filters.
There should not be that big different, can you post a test that fills
elasticsearch with data and recreates it? Note that the first time
executing
it might take time, second executions should be faster.
I'm trying to use the new named filters feature in 0.11 and getting a
QueryParsingException on this query:
I haven't tried these yet, but looking at the issuehttp://github.com/elasticsearch/elasticsearch/issues/issue/364
it seems that you should put the "_name" inside the filter:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.