Starting in Cloudera Enterprise 6, Cloudera provides a Solr configuration migration script to simplify the upgrade process by providing upgrade instructions tailored to yourĬonfiguration. Additionally, admins had to determine whether theyĬould upgrade existing indexes, or if they had to re-index the raw data. Review the Solr release notes and manually identify configuration changes needed to address incompatibilities or to take advantage of new features.
It has long been a challenge to understand the implications of a Solr upgrade. Do not upgrade your production Cloudera Search environments to CDH 6 until you have tested the migrated configuration with CDH 6 on a testing or development cluster.ĭespite widespread enterprise adoption, Solr lacks automated upgrade tooling. Warning: Although the configuration migration script addresses known incompatibilities, there might be incompatible configurations that are notĭetected by the script.
Solr Configuration Migration Script Overview You can continue indexing to existing collections (except Lily HBase indexing) until otherwise instructed. Do not create, delete, or modify any collections for the duration of the migration and upgrade.
For instructions, see Migrating HBase Indexer Sentry Policy Files to the Sentry Service. CDH versions lower than 5.14.0 do not support using the Sentry Service with the HBase
#Cloudera apache lucene update#
The following procedures update only your Solr configuration and metadata to be compatible with the new Solr version. Warning: Due to changes in the underlying Apache Lucene file format between the CDH 5 and CDH 6 versions of Solr, it is not possible to directly