[
https://issues.apache.org/jira/browse/METRON-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068492#comment-16068492
]
ASF GitHub Bot commented on METRON-947:
---
GitHub user ottobackwards opened a pull request:
https://github.com/apache/metron/pull/626
METRON-947 [DO NOT MERGE UNTIL METRON-942] Stellar Management Function for
Metron Parser Extension Configurations
METRON-777 adds the Metron Extension capability, the default parsers as
extensions, and the parser archetype
METRON-942 adds metron-rest support for installing and uninstalling parser
extensions, as well as the configuration primitives for extensions in zookeeper
This PR adds a Stellar Management command to retrieve those configurations.
## Testing
### Build and install some parser extensions
Follow the test plan for
[METRON-942](https://github.com/apache/metron/pull/580), to the point where you
have built and installed one or more parser extensions.
### deploy the metron-management jar per readme
### Run Stellar
```bash
[vagrant@node1 ~]$ /usr/metron/0.4.0/bin/stellar -z node1:2181
```
Run the command:
```bash
CONFIG_GET('PARSER_EXTENSION', 'metron-parser-nice-assembly-0_4_0')
```
verify that the configuration return matches what you would see in the rest
client
if you executed Parser Extension Controller : get
/api/v1/ext/parsers/{name} -> name = metron-parser-nice-assembly-0_4_0
### For all changes:
- [ 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- where 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)?
### For code changes:
- [na ] 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 incubating-metron folder via:
```
mvn -q clean integration-test install && build_utils/verify_licenses.sh
```
- [x ] Have you written or updated unit tests and or integration tests to
verify your changes?
- [ na] 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:
- [ ] 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
```
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ottobackwards/metron METRON-947
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/626.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 #626
commit 864d320d91c522dfc2eb63fc12341f316a3f8952
Author: Otto Fowler
Date: 2017-03-17T04:56:49Z
Metron Extension system
Based on Apache Nifi Nars
NAR changes
* new lib , rebrand to bundles from NAR
* port to VFS/FileObject from File based
* ability to set property values
* Rework FileUtils so that you can derive and override
* added initializers to set 'classes' that we care about instead of hard
coding them, still needs defaults
* added components nec. for integration tests ( do not want dep. on
metron-* )
* VFSClassloader for NarClassLoader
* Hdfs based integration test version of unpacknars tests
* HDFS ( filesystem ) based fileutilities to cover for writes to hdfs,
since VFS is currently R/O HDFS
* modified plugin to support configuration of outputs
* use c
