Filtered Query Standard Analyzer Stopword Problem


(frazer) #1

When doing a filtered query search for a stopword I get a shard
failure error.

Reproducible below.

curl -XPUT 'http://localhost:9200/twitter/tweet/1' -d '{
"user" : "kimchy",
"post_date" : "2009-11-15T14:12:12",
"message" : "trying out Elastic Search"
}'

curl -XGET 'http://localhost:9200/twitter/_search?pretty=true' -d
'
{"query" : { "filtered" : {"query" : {"term" : {"user" : "kimchy"}},
"filter" : {"and" : [{"term" : {"id" : 1}}, {"query":
{"query_string" : { "default_field": "message", "query" :
"the"}}} ]}}}}'

{
"took" : 3,
"timed_out" : false,
"_shards" : {
"total" : 5,
"successful" : 4,
"failed" : 1,
"failures" : [ {
"index" : "twitter",
"shard" : 2,
"reason" : "QueryPhaseExecutionException[[twitter][2]:
query[filtered(id:1)-

org.elasticsearch.common.lucene.search.AndFilter@bf6de680],from[0],size[10]:
Query Failed [Failed to execute main query]]; nested: "
} ]
},
"hits" : {
"total" : 0,
"max_score" : null,
"hits" : [ ]
}
}

If I change my search term to anything other than a stopword all is
well.

Am I right to assume this is a bug?

Thanks

Frazer


(Shay Banon) #2

Yes, this is a bug, can you open an issue for it?
On Friday, April 29, 2011 at 7:53 PM, frazer wrote:

When doing a filtered query search for a stopword I get a shard
failure error.

Reproducible below.

curl -XPUT 'http://localhost:9200/twitter/tweet/1' -d '{
"user" : "kimchy",
"post_date" : "2009-11-15T14:12:12",
"message" : "trying out Elastic Search"
}'

curl -XGET 'http://localhost:9200/twitter/_search?pretty=true' -d
'
{"query" : { "filtered" : {"query" : {"term" : {"user" : "kimchy"}},
"filter" : {"and" : [{"term" : {"id" : 1}}, {"query":
{"query_string" : { "default_field": "message", "query" :
"the"}}} ]}}}}'

{
"took" : 3,
"timed_out" : false,
"_shards" : {
"total" : 5,
"successful" : 4,
"failed" : 1,
"failures" : [ {
"index" : "twitter",
"shard" : 2,
"reason" : "QueryPhaseExecutionException[[twitter][2]:
query[filtered(id:1)-

org.elasticsearch.common.lucene.search.AndFilter@bf6de680],from[0],size[10]:
Query Failed [Failed to execute main query]]; nested: "
} ]
},
"hits" : {
"total" : 0,
"max_score" : null,
"hits" : [ ]
}
}

If I change my search term to anything other than a stopword all is
well.

Am I right to assume this is a bug?

Thanks

Frazer


(Shay Banon) #3

Ok, opened an issue for it: https://github.com/elasticsearch/elasticsearch/issues/892.
On Friday, April 29, 2011 at 8:28 PM, Shay Banon wrote:

Yes, this is a bug, can you open an issue for it?
On Friday, April 29, 2011 at 7:53 PM, frazer wrote:

When doing a filtered query search for a stopword I get a shard
failure error.

Reproducible below.

curl -XPUT 'http://localhost:9200/twitter/tweet/1' -d '{
"user" : "kimchy",
"post_date" : "2009-11-15T14:12:12",
"message" : "trying out Elastic Search"
}'

curl -XGET 'http://localhost:9200/twitter/_search?pretty=true' -d
'
{"query" : { "filtered" : {"query" : {"term" : {"user" : "kimchy"}},
"filter" : {"and" : [{"term" : {"id" : 1}}, {"query":
{"query_string" : { "default_field": "message", "query" :
"the"}}} ]}}}}'

{
"took" : 3,
"timed_out" : false,
"_shards" : {
"total" : 5,
""successful" : 4,
"failed" : 1,
"failures" : [ {
"index" : "twitter",
"shard" : 2,
""reason" : "QueryPhaseExecutionException[[twitter][2]:
query[filtered(id:1)-

org.elasticsearch.common.lucene.search.AndFilter@bf6de680],from[0],size[10]:
Query Failed [Failed to execute main query]]; nested: "
} ]
},
"hits" : {
"total" : 0,
"max_score" : null,
"hits" : [ ]
}
}

If I change my search term to anything other than a stopword all is
well.

Am I right to assume this is a bug?

Thanks

Frazer


(system) #4