That did it, good sirs. Additionally, debugQuery=true no longer gives me an NPE.
Best Regards,
Jeff
On Nov 8, 2012, at 11:17 AM, Timothy Potter wrote:
> I've seen the same exact behavior when using analyzed key fields, switching
> to string as Erick recommends should solve your problem.
>
> Che
Thanks for looking at it.
Id is usually going to be as follows:
"some.domain.name_SOMELONGSHA1HASH:/FileName.ext/somechars/1"
I indexed it so I could search for the domain name or the hash without storing
it a second time. I'll convert to a string and see if this fixes the problem.
On Nov 8, 2
I've seen the same exact behavior when using analyzed key fields, switching
to string as Erick recommends should solve your problem.
Cheers,
Tim
On Thu, Nov 8, 2012 at 7:45 AM, Erick Erickson wrote:
> Hmmm, I tried this with a 2 shard cluster and it works just fine, using
> your schema, solrconf
Hmmm, I tried this with a 2 shard cluster and it works just fine, using
your schema, solrconfig and query so I'm puzzled. What happens when you
look at your cluster with the admin page? When you dive into collection1,
does it show any documents?
Also, look at admin/schema-browser and look at the a
I have a cluster of 6 shards of Solr 4.0.0 deployed, one machine each, with no
replicas, and another single machine running a zookeeper ensemble of 5. Using
python sunburnt, I submit six documents with separate ids and populated text
fields and commit them. No errors are reported. When I search
