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

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

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

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