[
https://issues.apache.org/jira/browse/SOLR-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445166#comment-13445166
]
Yonik Seeley commented on SOLR-3773:
------------------------------------
I'd go as far as to strongly recommend people use string as the type of their
ID field.
Some of the ways I've thought about doing cloud in conjunction with nested
documents and document blocks involves encoding sub-children as
The original idea around letting people specify their own uniqueKey field and
fieldType was that you could design a Solr schema that would be compatible with
a random lucene index. I think that's rapidly becoming an outdated idea, and
not worth the issues it causes.
> Hash based on the external String id rather than the indexed representation
> for distributed updates.
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-3773
> URL: https://issues.apache.org/jira/browse/SOLR-3773
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0, 5.0
>
>
> This makes some things easier - such as external systems doing the hashing
> themselves (like CloudSolrServer).
> It will be back compat for String id types but not others. Sent an email to
> the list a good time back seeing if this would bother anyone too much and got
> no replies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
