Ah, you mention most of the SolrCloud ones don't look like a problem.
The other two then:
1. RealTimeGetComponent - doesn't look like a schema field usage, don't see a
problem.
2. HashBasedRouter - looks like it could be a problem and this is new for 4.1 -
this is something we should document w
A search for "id" is much too broad. I looked at 3 of the SolrCloud classes you
mention and none of those "id"'s have anything to do with the unique field in
the schema. I have not looked at the hash based router, but if you find a real
issue then please file a JIRA issue.
- Mark
On Feb 12, 2
On 2/12/2013 7:54 PM, Shawn Heisey wrote:
On 2/11/2013 7:47 PM, Mark Miller wrote:
Doesn't sound right to me. I'd guess you heard wrong.
I did a search for "id" with the quotes throughout the branch_4x source
code. After excluding test code, test files, and other things that
looked like they
On 2/11/2013 7:47 PM, Mark Miller wrote:
Doesn't sound right to me. I'd guess you heard wrong.
I did a search for "id" with the quotes throughout the branch_4x source
code. After excluding test code, test files, and other things that
looked like they have good reason to be hardcoded, I was l
Apparently this was a side effect of the custom sharding feature.
There is a fix planned, but I don't know more about it than that.
Michael Della Bitta
Appinions
18 East 41st Street, 2nd Floor
New York, NY 10017-6271
www.appinions.com
Where Influ
Doesn't sound right to me. I'd guess you heard wrong.
- mark
Sent from my iPhone
On Feb 11, 2013, at 7:15 PM, Shawn Heisey wrote:
> I have heard that SolrCloud may require the presence of a uniqeKey field
> specifically named 'id' for sharding.
>
> Is this true? Is it still true as of Solr
I have heard that SolrCloud may require the presence of a uniqeKey field
specifically named 'id' for sharding.
Is this true? Is it still true as of Solr 4.2-SNAPSHOT? If not, what
svn commit fixed it? If so, should I file a jira? I am not actually
using SolrCloud for one index, but my worr
