Hi Nick, I was not sure about the implementation, so does it generally mean everywhere I can use Stellar DSL, all of the functions have been implemented and ready to use?
Cheers, Ali On Thu, May 25, 2017 at 2:52 AM, Nick Allen <[email protected]> wrote: > > can I do the concatenation on the fly at the enrichment level, so I > don't need to store this temp field in Elasticsearch/HDFS. > > Sure, absolutely. > > > Moreover, I need to have a conditional enrichment to say if you > couldn't find any match for "tenant_name+device_type+device_name" lookup > for "tenant_name+device_type+default_device". > > Yes, you can. You've got if/else, JOIN, IS_EMPTY, and others that should > make implementing this logic pretty easy. > > > > > On Tue, May 23, 2017 at 10:34 PM, Ali Nazemian <[email protected]> > wrote: > >> Hi, >> >> I was wondering how I can manage Stellar syntax to be aligned with the >> following structure for the HBase enrichment: >> >> HBase_row_key: tenant_name+device_type+device_name >> >> At the high-level, I need to create a separate field via a post-parse >> Stellar function to be a concatenation of tenan_name, device_type and >> device_name. Let's call this field "key". Basically, I need to do the >> enrichment on the "key" which would be corresponding to the HBase row key. >> My first question is *can I do the concatenation on the fly at the >> enrichment level, so I don't need to store this temp field in >> Elasticsearch/HDFS*. >> >> Moreover, I need to have a conditional enrichment to say if you couldn't >> find any match for "tenant_name+device_type+device_name" lookup for >> "tenant_name+device_type+default_device". The second question would be *how >> can I manage conditional enrichment like this one*. I would be really >> grateful if you can provide some example. >> >> Regards, >> Ali >> > > -- A.Nazemian
