[
https://issues.apache.org/jira/browse/METRON-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427705#comment-16427705
]
ASF GitHub Bot commented on METRON-1499:
----------------------------------------
GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/984
METRON-1499 Enable Configuration of Unified Enrichment Topology via Ambari
We recently introduced an alternative enrichment topology; the Unified
enrichment topology. This is an alternative to the existing Split Join
topology. This work enhances the MPack so that a user can configure, stop, and
start either the Unified or the Split Join enrichment topology.
* Each topology has a separate configuration section under the Metron >
Enrichment settings in Ambari.
* A combo box allows the user to choose which Enrichment topology should be
run.
* The Split Join topology remains the default Enrichment topology.
* The `bin/start_enrichment_topology.sh` script was enhanced so that you
can pass in the `--filter` and `--remote` args directly to launch an
alternative topology. Running the script with no parameters will launch the
default topology; Split Join.
* The Unified topology had previously reused some of the same settings from
the Split Join topology. Where it made sense, the Unified topology was updated
to use its own logically named properties.
* There are now separate properties file for each Enrichment topology.
`$METRON_HOME/config/enrichment-splitjoin.properties`
`$METRON_HOME/config/enrichment-unified.properties`
* There are separate flux files for each Enrichment topology.
`$METRON_HOME/flux/enrichment/remote-splitjoin.yaml`
`$METRON_HOME/flux/enrichment/remote-unified.yaml`
### Manual Testing
To test this change, launch a development environment. The Split Join
Enrichment topology will be running by default. Switch to the Unified
topology. Change some settings and make sure they are reflected in the
topology.
## 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?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/metron METRON-1499
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/984.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #984
----
commit 67735e0dd2ac119d826f08e5abb820438382381c
Author: Nick Allen <nick@...>
Date: 2018-04-05T15:56:36Z
METRON-1499 Enable Configuration of Unified Enrichment Topology via Ambari
----
> Enable Configuration of Unified Enrichment Topology via Ambari
> --------------------------------------------------------------
>
> Key: METRON-1499
> URL: https://issues.apache.org/jira/browse/METRON-1499
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
>
> We recently introduced an alternative enrichment topology that is being
> called the "Unified" enrichment topology. This is an alternative to the
> existing "Split Join" topology.
>
> We need to enhance the MPack so that a user can configure, stop, and start
> either the "Unified" or the "Split Join" enrichment topology.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
