merrimanr opened a new pull request #1441: METRON_2156: Remove Storm dependency from metron-hbase URL: https://github.com/apache/metron/pull/1441 ## Contributor Comments This primary purpose of this PR is to remove the Storm dependencies from metron-hbase. ### Changes Included - The metron-hbase module was split into metron-hbase-common and metron-hbase-storm - Package for `ColumnList`, `IColumn` and `ICounter` classes changed and moved to metron-hbase-common since they has no dependency on Storm - Package for `Widget` and `WidgetMapper` classes changed and moved to metron-hbase-storm since they are only used by classes in that module - Refactored Storm dependencies and related classes out of `HBaseClientTest` - Removed unused classes `TupleTableConfig`, `MockHBaseConnector`, and `HTableConnector` ### Testing This has been tested in full dev. I focused on testing HBase client interactions in Stellar and REST. #### Load an enrichment Load the `alexa` enrichment with the `flatfile_loader.sh` script. 1. Download the alexa data set and put it in HDFS: ``` su - metron source /etc/default/metron wget http://s3.amazonaws.com/alexa-static/top-1m.csv.zip unzip top-1m.csv.zip head -n 10000 top-1m.csv > top-10k.csv hdfs dfs -put top-10k.csv /tmp 2. Load the enrichment: vi extractor.json { "config": { "columns": { "domain": 1, "rank": 0 }, "indicator_column": "domain", "separator": ",", "type": "alexa" }, "extractor": "CSV" } $METRON_HOME/bin/flatfile_loader.sh -i /tmp/top-10k.csv -t enrichment -c t -e ./extractor.json -m MR exit ``` #### Verify REST To verify REST is working correctly: 1. Get a list of available enrichments. `alexa` should be in the list: ``` [root@node1 vagrant]# curl -X GET --header 'Accept: application/json' 'http://user:password@node1:8082/api/v1/sensor/enrichment/config/list/available/enrichments' ["alexa"] ``` 2. Store user settings: ``` curl -X POST --header 'Content-Type: application/json' --header 'Accept: */*' -d '{ "facetFields": [ "test" ] }' 'http://user:password@node1:8082/api/v1/alerts/ui/settings' ``` and read them back: ``` [root@node1 vagrant]# curl -X GET --header 'Accept: application/json' 'http://user:password@node1:8082/api/v1/alerts/ui/settings' {"user":null,"tableColumns":null,"savedSearches":null,"facetFields":["test"]} ``` #### Verify Stellar Start the Stellar shell with `/usr/metron/0.7.2/bin/stellar --zookeeper node1:2181`. 1. Verify the `ENRICHMENT_GET` function works correctly: ``` [Stellar]>>> ENRICHMENT_GET('alexa', 'google.com', 'enrichment', 't') {domain=google.com, rank=1} ``` 2. I tested Stellar against different jars by creating `/usr/metron/0.7.2/contrib`, copying `metron-<module name>-storm*.jar`s and executing the `ENRICHMENT_GET` function. I tested with `enrichment`, `profiler`, and `parsing`. This should similar Stellar in the various topologies. ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) 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](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). - [ ] 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: - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed? - [x] Have you included steps or a guide to how the change may be verified and tested manually? - [x] 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 ``` - [x] Have you written or updated unit tests and or integration tests to verify your changes? - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] 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: - [x] 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 ``` - [x] Have you ensured that any documentation diagrams have been updated, along with their source files, using [draw.io](https://www.draw.io/)? See [Metron Development Guidelines](https://cwiki.apache.org/confluence/display/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](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
