Member since
08-21-2013
146
Posts
25
Kudos Received
34
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3053 | 10-24-2016 10:43 AM | |
6687 | 03-13-2016 02:15 PM | |
3488 | 12-11-2015 01:48 AM | |
2912 | 11-23-2015 12:11 PM | |
2697 | 07-06-2015 10:40 AM |
11-18-2014
01:41 AM
1 Kudo
You need to change your xquery command to wrap your XML output into yet another XML element (e.g. “record”). For example, in order to generate a morphline record with a “myFoo" field that contains “foo", as well as a “myBar" field that contains “bar", your xquery command should be formulated such that it outputs an XML fragment like this: <record> <myFoo>foo</myFoo> <myBar>bar</myBar> </record>
... View more
11-10-2014
07:10 AM
The "if" command and "equals" command and indeed all morphline commands know nothing about hbase colunmns or hbase qualifiers, except for the extractHBaseCells command. Use extractHBaseCells to extract whatever hbase columns you want into whatever morphline record fields you want, then subsequently use "if", "equals" or similar to act on the morphline record fields (not on hbase columns or qualifiers direcly).
... View more
11-10-2014
03:32 AM
Try equals { id : [] } for example as shown here: http://kitesdk.org/docs/current/kite-morphlines/morphlinesReferenceGuide.html#if In a morphline record there is no difference between a field with zero values and a field that doesn't exist.
... View more
11-09-2014
12:35 PM
You can express it all in a single morphline. Consider using if-then-else command or the tryRules command or similar in order to check which case applies and execute whatever corresponding logic is appropriate for that case. You can have multiple extractHBaseCells commands in a single morphline, e.g. one in each branch of the tryRules command. Wolfgang.
... View more
11-06-2014
03:39 AM
It’s mentioned in the ref guide for the next upcoming kite version per https://github.com/kite-sdk/kite/blob/master/kite-morphlines/src/site/confluence/morphlinesReferenceGuide.confluence#L2879-L2889
... View more
11-05-2014
10:42 AM
The xquery command expects a byte[] rather than a string as input, and that input must be in the outputField : “_attachment_body” field rather than the "data" field. Try changing the extractHBaseCells command to use type : "byte[]” and outputField : “_attachment_body" Also you need to change your xquery command to wrap your XML output into yet another XML element (e.g. “record”). For example, in order to generate a morphline record with a “myFoo" field that contains “foo", as well as a “myBar" field that contains “bar", your xquery command should be formulated such that it outputs an XML fragment like this: <record> <myFoo>foo</myFoo> <myBar>bar</myBar> </record> Wolfgang.
... View more
11-04-2014
12:33 PM
Try /var/log/solr
... View more
11-04-2014
12:49 AM
The solr schema.xml config file needs to conform to the documents that you are trying to insert. Try adjusting schema.xml accordingly and tell solr about it via the solrctl CLI. Also see http://kitesdk.org/docs/current/kite-morphlines/morphlinesReferenceGuide.html#sanitizeUnknownSolrFields XPath and XQuery docs are here: http://kitesdk.org/docs/current/kite-morphlines/morphlinesReferenceGuide.html#xquery The log files of the Solr server and MapReduce tasks, etc can be displayed in the Cloudera Manager GUI. Wolfgang.
... View more
10-17-2014
12:05 AM
Basically, yes. Beyon see there are a gazillion text templating tools already out there, e.g. freemarker et al. No need to reinvent the wheel.
... View more
10-17-2014
12:02 AM
bq. For example, if one compiles 10 morphlines from the same config file and then run each of those in a separate thread, can that cause any thread safety issues? There?s no thread safety issue when doing that. (And there?s minimal contention as well, which improves throughput). In fact, that?s exactly what the hbase-indexer does in order to take advantage of multiple CPU cores, and that?s also what users of the Flume Morphline Solr Sink sometimes do. Wolfgang.
... View more