Re: Metron HBase conditional enrichment

That sheds light. Thanks, Nick. --Matt From: Nick Allen Reply-To: "user@metron.apache.org" Date: Thursday, May 25, 2017 at 3:06 PM To: "user@metron.apache.org" Subject: Re: Metron HBase conditional enrichment Each topology

Re: Metron HBase conditional enrichment

Each topology has its own uber-jar that is built from all of it's dependencies. It's classpath is basically whatever is in the uber-jar. That's why running with -pl against the project from which the uber jar is built should identify the Stellar functions available to each topology. When

Re: AWS deployment with 5 hosts.

What host groups did ec2-34-210-245-155.us-west-2.compute.amazonaws.com get assigned to? You can look at the labels that get attached to the host in the EC2 web interface. I have a feeling it has something to do with the Ambari blueprint that is used (see

AWS deployment with 5 hosts.

Deploying the standard 10 instance setup works. However, for our current needs, 10 m4.xlarge instances seem overkill and we want to deploy Metron on only 5 hosts for now. I would think that editing metron/metron-deployment/amazon-ec2/playbook.yml would be enough. I changed the following:

Re: Metron HBase conditional enrichment

I think most of those restricted functions are in the metron-managment section. On May 25, 2017 at 07:27:24, Nick Allen (n...@nickallen.org) wrote: > everywhere I can use Stellar DSL, all of the functions have been implemented and ready to use? Generally, yes, you are right. I vaguely