nickwallen opened a new pull request #1448: METRON-2164 Remove the Split-Join 
Enrichment Topology
URL: https://github.com/apache/metron/pull/1448
 
 
   The Split-Join Enrichment topology has been deprecated since November 2018. 
Metron defaults to using the Unified Enrichment topology currently.  This PR 
completely removes the Split-Join topology from the code base.
   
   Here is the [original discuss thread 
](https://lists.apache.org/thread.html/6cfc883de28a5cb41f26d0523522d4b93272ac954e5713c80a35675e@%3Cdev.metron.apache.org%3E)on
 deprecation.
   
   ## Testing
   
   1. Launch the CentOS 6 development environment.
   
   1. Ensure telemetry is being indexed and can be found via the Alerts UI.
   
   1. Go to Ambari > Metron > Configs > Enrichment > Topology and change some 
of the settings on this panel.  Restart the Enrichment topology and ensure that 
the settings have taken effect.
   
   1. Again, ensure telemetry is being indexed and indirectly that the 
Enrichment topology restarted correctly.
   
   ## Pull Request Checklist
   
   - [ ] 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)?
   - [ ] 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:
    
   - [ ] 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](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