METRON-2238: Streaming enrichments regression

[merrimanr]

Contributor Comments

This PR fixes a small regression in the streaming enrichments use case. The issue happens specifically when a org.apache.metron.writer.hbase.SimpleHbaseEnrichmentWriter class is configured as the writer class in a parser topology. The fix is to explicitly set the guava dependency to the version HBase depends on.

Testing

Spin up full dev and configure a streaming enrichment.

1. Create a user config with the writer set to SimpleHbaseEnrichmentWriter:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{
 "parserClassName" : "org.apache.metron.parsers.csv.CSVParser"
 ,"writerClassName" : "org.apache.metron.writer.hbase.SimpleHbaseEnrichmentWriter"
 ,"sensorTopic":"user"
 ,"parserConfig":
 {
    "shew.table" : "enrichment"
   ,"shew.cf" : "t"
   ,"shew.keyColumns" : "ip"
   ,"shew.enrichmentType" : "user"
   ,"columns" : {
      "user" : 0
     ,"ip" : 1
                }
 }
}' 'http://node1:8082/api/v1/sensor/parser/config/user'

2. Start the user parser topology:

source /etc/default/metron
$METRON_HOME/bin/start_parser_topology.sh -s user -z $ZOOKEEPER -k $BROKERLIST

3. Create a user topic and send enrichment data:

/usr/hdp/current/kafka-broker/bin/kafka-topics.sh --create --zookeeper $ZOOKEEPER  --replication-factor 1 --partitions 1 --topic user
echo "user,192.168.1.1" | /usr/hdp/current/kafka-broker/bin/kafka-console-producer.sh --broker-list $BROKERLIST --topic user

There should be user enrichment data in hbase and no errors in the user parser topology.

Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.

In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:

For all changes:

• Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
• Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
• Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

• Have you included steps to reproduce the behavior or problem that is being changed or addressed?

• Have you included steps or a guide to how the change may be verified and tested manually?

• Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:

  mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
  

• Have you written or updated unit tests and or integration tests to verify your changes?

• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

• Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:

  cd site-book
  mvn site
  

• Have you ensured that any documentation diagrams have been updated, along with their source files, using draw.io? See Metron Development Guidelines for instructions.

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

[mmiklavc]

What's our guarantee this change won't have implications in other places? What projects or other uber jars depend on this module?

[merrimanr]

As far as I know there are no modules that depend on metron-parsing-storm. If we focus on testing parser topologies then we should be covered.

[mmiklavc]

I'm going to run through this test as well - https://cwiki.apache.org/confluence/display/METRON/2016/04/25/Metron+Tutorial+-+Fundamentals+Part+1:+Creating+a+New+Telemetry. I saw some issues while testing another PR and would like to be able to better isolate it.

[mmiklavc]

Ran through the streaming enrichment case as well as the basic squid parser case. Looks good to me, +1.