Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
CloudSolrServer.setIdField seems innocent enough, but the way it's used is purely for routing. CloudSolrServer doesn't actually care what the ID field is. The default document routing is indeed on the ID but it can be changed.
For back-compat; it can stay but be deprecated. I propose a setRouteField replacement.