Behavioral Changes in Cloudera Search
Learn about the change in certain functionality of Cloudera Search that has resulted in a change in behavior from the previously released version to this version of Cloudera Runtime.
- Validation of
javax.security.auth.useSubjectCredsOnlyparameter changed in Solr client
- Previous behavior:
Unless explicitely set to 'true', Solr client used to set the value of javax.security.auth.useSubjectCredsOnly parameter to 'false'.
- New behavior:
Solr client does not overwrite ‘null’ value of javax.security.auth.useSubjectCredsOnly parameter, it only throws a warning during connection setup:
System Property: javax.security.auth.useSubjectCredsOnly set to: [true|null] not false. SPNego authentication may not be successful.
This may cause issues when connecting Solr to custom applications. To prevent this, you need to set
in the JVM configuration of those applications. Cloudera has implemented this change in MapReduceIndexer, CrunchIndexer, Spark-Solr, Hive-Solr connector, and Atlas.