[SOLR-11983] No indication in CloudSolrClient for missing id field

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 6.5.1
• Component/s: SolrJ
• Assignee: Unassigned
• Reporter: Dean Gurvitz
• Created: 14/Feb/18 09:02
• Updated: 08/Jun/19 15:15

Description

It appears that when indexing a document using CloudSolrClient that misses the "id" field, no indication, exception or warning is given at any point, and the document is indexed using a regular load-balancing approach. This can be very detrimental in collections where the id field has a different name and the indexing client forgot to call the "setIdField" method, causing an indexing performance hit with no apparent explanation.

The documentation requires that the "setIdField" method be called in case the id field is named differently, and therefore the code should reflect this requirement in at least some way.

I have only tested this on SolrJ 6.5.1, but from a brief look it appears that this behavior probably applies to SolrJ 7+.

 

Issue Links

• relates to: SOLR-11868 Deprecate CloudSolrClient.setIdField, use information from Zookeeper