About whosch

whosch · ‎04-29-2014

A next step is to configure Solr, in particular schema.xml and solrconfig.xml. For an example see http://www.cloudera.com/content/cloudera-content/cloudera-docs/Search/latest/Cloudera-Search-User-Guide/csug_tutorial.html

whosch · ‎04-25-2014

Yes, you can write a custom morphline command in Java [1] and add the corresponding custom jar that to the classpath, e.g via the HBASE_INDEXER_CLASSPATH environment variable in menu ?Service-Wide/Advanced/Safety Valve? in Cloudera Manager (for Near Real Time Indexing) or via the --libjars CLI option on HBaseMapReduceIndexerTool (for Batch Indexing). Alternatively, you also write a mini script in Java and paste it into the body of the ?java" morphline command [2]. [1] Section "Implementing your own Custom Command? at http://cloudera.github.io/cdk/docs/current/cdk-morphlines/morphlinesReferenceGuide.html [2] http://cloudera.github.io/cdk/docs/current/cdk-morphlines/morphlinesReferenceGuide.html#/java

whosch · ‎04-24-2014

You can just specify an extractHBaseCells command followed by an xquery command in the same morphline config file. Each command pipes into the subsequent command, and you can specify as many commands as you like. The links I mentioned contain a (commented out) example for extractHBaseCells followed by readAvroContainer. just uncomment that and replace readAvroContainer with xquery. Wolfgang.

whosch · ‎04-24-2014

See Sections "Creating a Morphline Configuration File? and "Understanding the extractHBaseCells morphline command? at http://www.cloudera.com/content/cloudera-content/cloudera-docs/Search/latest/Cloudera-Search-User-Guide/csug_hbase_batch_indexer.html Wolfgang.

whosch · ‎04-17-2014

Sounds like the --zookeeper arg is missing. See http://www.cloudera.com/content/cloudera-content/cloudera-docs/Search/latest/Cloudera-Search-User-Guide/csug_use_hbase_indexer_service.html

whosch · ‎02-07-2014

Make sure to run search-1.1.0.

whosch · ‎02-07-2014

I think this has been fixed in more recent versions of Cloudera Search.

whosch · ‎02-02-2014

All variables have to statically resolve at compile time. Still, you can statically enumerate multiple solrLocators and do stuff like this: if { conditions : [ { equals { tenant : [foo] } } ] then : [ { loadSolr { solrLocator : { collection : collection_foo, zkHost : "127.0.0.1:2181/solr" } } } ] else : [ { loadSolr { solrLocator : { collection : collection_bar, zkHost : "127.0.0.1:2181/solr" } } } ] } Wolfgang.

whosch · ‎01-28-2014

Cool!

whosch · ‎01-27-2014

There's no need to change any input data. Rather you need to change the xsl transform to spit out whatever output is expected. The XSL transform needs to produce data that is shaped as expected by the rules that govern the conversion of saxon xslt output to morphline records, as described in the docs - http://kitesdk.org/docs/current/kite-morphlines/morphlinesReferenceGuide.html#/xslt Wolfgang.

Online	Offline
Last Visited	‎06-08-2016 05:03 PM

Member Since	‎08-21-2013 12:00 PM
Last Visited	‎06-08-2016 05:03 PM
Posts	146
Kudos received	25

Cloudera Community

Re: Lily Indexer: ensuring Hbase and Solr record c...

Re: readJsonTweets Morphline using the MapReduceIn...

Re: Indexing data to Solr with a MapReduce and Mor...

Re: Configure the Lily HBase indexer to index cert...

Re: Key-Value Store Indexer for NRT with number of...

Re: Extract hbase cell command reference guide

Re: Extract hbase cell command reference guide

Re: Extract hbase cell command reference guide

Re: Extract hbase cell command reference guide

Re: Error when registering a lily indexer

Re: Avro type information shown with indexed field...

Re: Avro type information shown with indexed field...

Re: set morphline variable from if command

Re: Morphline XSLT not working as described

Re: Morphline XSLT not working as described