Re: Query OR operator triggers weird exception

2013-10-31 Thread michael.boom
After restarting my servers this was the first error i got when trying to make the same query: { "responseHeader":{ "status":500, "QTime":336, "params":{ "lowercaseOperators":"true", "indent":"true", "q":"text:\"blue cat\"", "distrib":"false", "stopword

Re: Query OR operator triggers weird exception

2013-10-31 Thread michael.boom
I also narrowed my problem to the text field. simple query : title:"red shoes" works but text:"red shoes" does not. Could you extend a little bit how could my schema omitted position information? I'm not really sure what you mean by that. Thank you! - Thanks, Michael -- View this

Re: Query OR operator triggers weird exception

2013-10-31 Thread michael.boom
Thanks Jack! Some more info: I looked a little bit and tried the problem query, undistributed, on each shard: shard2_replica1 and shard2_replica2 throw this error: "responseHeader":{ "status":500, "QTime":2, "params":{ "lowercaseOperators":"true", "indent":"true", "q":

Re: Query OR operator triggers weird exception

2013-10-31 Thread Jack Krupansky
Maybe your schema has "omitted" position information for the "text" field which is required to query phrases. That would throw an exception on every server for a distributed query. Still, that does seem like an odd exception for a simple query problem. -- Jack Krupansky -Original Message-