[
https://issues.apache.org/jira/browse/SOLR-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165365#comment-17165365
]
ASF subversion and git services commented on SOLR-11868:
--------------------------------------------------------
Commit f9410e14614d1f9ebb88226c287f38cd4d0b3d1f in lucene-solr's branch
refs/heads/branch_8x from Erick Erickson
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f9410e1 ]
SOLR-11868: CloudSolrClient.setIdField is confusing, it's really the routing
field. Should be deprecated.
> Deprecate CloudSolrClient.setIdField, use information from Zookeeper
> --------------------------------------------------------------------
>
> Key: SOLR-11868
> URL: https://issues.apache.org/jira/browse/SOLR-11868
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 7.2
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
>
> IIUC idField has nothing to do with the <uniqueKey> field. It's really
> the field used to route documents. Agreed, this is often the "id"
> field, but still....
> In fact, over in UpdateReqeust.getRoutes(), it's passed as the "id"
> field to router.getTargetSlice() and just works, even though
> getTargetSlice is clearly designed to route on a field other than the
> <uniqueKey> if we didn't just pass null as the "route" param.
> The confusing bit is that if I have a route field defined for my
> collection and want to use CloudSolrClient I have to figure out that I
> need to use the setIdField method to use that field for routing.
>
> We should deprecate setIdField and refactor how this is used (i.e.
> getRoutes). Need to beef up tests too I suspect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
