Dean Gurvitz created SOLR-11983: ----------------------------------- Summary: No indication in CloudSolrClient for missing id field Key: SOLR-11983 URL: https://issues.apache.org/jira/browse/SOLR-11983 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: SolrJ Affects Versions: 6.5.1 Reporter: Dean Gurvitz
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+. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org