nickwallen opened a new pull request #1484: METRON-2218 Upgrade Data Management 
for HBase 2.0.2
URL: https://github.com/apache/metron/pull/1484
 
 
   This change upgrades the core Enrichment components to work with HBase 
2.0.2.  This PR is for the `feature/METRON-2088-support-HDP-3.1` feature branch.
   
   This change should be tested in the CentOS 6 dev environment with HDP-2.6.  
These are backwards compatible HBase changes that require additional changes 
before everything can be compiled under HDP-3.1.
   
   This change depends on #1482 and will show boths sets of changes until that 
PR can be merged.
   
   ## Changes
   
   1. Updated the TAXII loader to use an `HBaseClient`.
   
   1. ..
   
   ## Acceptance Testing
   
   ### Basics
   
     Verify data is flowing through the system, from parsing to indexing
   
     1. Launch the development environment.
           ```
           cd metron-deployment/development/centos6
           vagrant up
           ```
   
     1. Open Ambari and navigate to the Metron service 
http://node1:8080/#/main/services/METRON/summary
   
     1. Open the Alerts UI
   
     1. Verify alerts show up in the main UI - click the search icon (you may 
need to wait a moment for them to appear)
   
     1. Head back to Ambari and select the Kibana service 
http://node1:8080/#/main/services/KIBANA/summary
   
     1. Open the Kibana dashboard via the "Metron UI" option in the quick links
   
     1. Verify the dashboard is populating
   
   ## Additional Instructions
   
   TODO
   
   ## Pull Request Checklist
   
   - [x] 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).
   - [x] 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.
   - [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
   - [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:
   - [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)?
   - [ ] Have you verified the basic functionality of the build by building and 
running locally with Vagrant full-dev environment or the equivalent?
   

----------------------------------------------------------------
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

Reply via email to