Interesting, that sounds like a bit of an issue really, the cloud is
"hiding" the real error. Presumably the non ok status: 500 (buried at the
bottom of your trace) was where the actual shard was returning the error
(we've had issues with positional stuff before and it normally says
something obvi
Thanks, I'll check that out.
Turns out our problem was we had omitTermFreqAndPositions true but were
running queries like "puppy dog" which, I would imagine, require position.
On Mon, Jan 21, 2013 at 9:22 PM, Gopal Patwa wrote:
> one thing I noticed in solrconfig xml that it set to use Lucene
one thing I noticed in solrconfig xml that it set to use Lucene version 4.0
index format but you mention you are using it 4.1
LUCENE_40
On Mon, Jan 21, 2013 at 4:26 PM, Brett Hoerner wrote:
> I have a collection in Solr 4.1 RC1 and doing a simple query like
> text:"puppy dog" is causing an
I have a collection in Solr 4.1 RC1 and doing a simple query like
text:"puppy dog" is causing an exception. Oddly enough, I CAN query for
text:puppy or text:"puppy", but adding the space breaks everything.
Schema and config: https://gist.github.com/f49da15e39e5609b75b1
This happens whether I quer
