Here is how it works with CM: Paste the contents of your morphline config file into the CM text box as described here: https://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Managing-Clusters/cmmc_adding_search_solr.html#concept_oww_yqf_hk_unique_1 Cloudera Manager automatically uploads and deploys said pasted morphline config to the Flume agent's process directory as "morphlines.conf" when it starts the Flume agent. Therefore, you can reference the morphline config file in the Flume agent's configuration file using only the (relative path) name. For example, in flume.conf you can use the name morphlines.conf to refer to the location of the morphlines configuration file. Wolfgang. ... View more

To print diagnostic information, such as the content of records as they pass through the morphline commands, consider enabling TRACE log level. For example, you might add the following lines to your log4j.properties file: log4j.logger.com.cloudera.cdk.morphline=TRACE In Cloudera Manager 4 this can be done by navigating to Services -> Flume -> Configuration -> View and Edit -> Agent (Default) -> Advanced -> Agent Logging Safety Valve, followed by a restart of the Flume service. For HBase Near Real Time Indexing it can be done as described near the bottom of this manual page: http://www.cloudera.com/content/cloudera-content/cloudera-docs/Search/latest/Cloudera-Search-User-Guide/csug_use_hbase_indexer_service.html Wolfgang ... View more

We are working on such a feature, should be available soon. Meanwhile you can work around it by touching all cells without significantly modifying them, e.g. by updating the timestamp. Wolfgang. ... View more

Looks like your solr version might be older than what we ship with Cloudera Search. I recommend upgrading to search-1.0.0. Wolfgang. ... View more