[GitHub] metron pull request #588: METRON-954: Create ability to change output topic ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/metron/pull/588


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] metron pull request #588: METRON-954: Create ability to change output topic ...

[cestella]

Github user cestella commented on a diff in the pull request:

https://github.com/apache/metron/pull/588#discussion_r116583655
  
--- Diff: 
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/SquidIntegrationTest.java
 ---
@@ -29,6 +29,11 @@ String getSensorType() {
   }
 
   @Override
--- End diff --

haha ok, you got it.  I'll adjust it tomorrow to be a different type of 
test and not piggyback on squid.  You're right, the parser tests are for 
testing the parsers, not testing the ancillary stuff, like kafka writers.  
Thanks for keeping me honest, @ottobackwards 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] metron pull request #588: METRON-954: Create ability to change output topic ...

[ottobackwards]

Github user ottobackwards commented on a diff in the pull request:

https://github.com/apache/metron/pull/588#discussion_r116583237
  
--- Diff: 
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/SquidIntegrationTest.java
 ---
@@ -29,6 +29,11 @@ String getSensorType() {
   }
 
   @Override
--- End diff --

I have a couple of things that come to mind, not all relevant:

* With 777 and 942, squid is a real parser extension, installed and usable 
etc.  So throwing in a test of something outside the parser into it's 
integration test, and making it _diffferent_ than the others seems not right to 
me.

* Same for any parser really.  The parsers tests are for testing the 
parsers.  You guys did a lot of work making the tests alike, and 
understandable, we should maintain that.

* If you don't change that, I don't think I'll have to do conflict work in 
777, which I continue to have to maintain ;) ( disregard this )


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] metron pull request #588: METRON-954: Create ability to change output topic ...

[cestella]

Github user cestella commented on a diff in the pull request:

https://github.com/apache/metron/pull/588#discussion_r116582169
  
--- Diff: 
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/SquidIntegrationTest.java
 ---
@@ -29,6 +29,11 @@ String getSensorType() {
   }
 
   @Override
--- End diff --

We could spin up a new integration test, but I thought this did the trick 
and didn't add the cost of another integration test to the build time.  

I do have a test ensuring the value gets passed through to the parser.  
This just completed the loop.  If we don't feel that an integration test is 
necessary here, then I can remove it too.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] metron pull request #588: METRON-954: Create ability to change output topic ...

[ottobackwards]

Github user ottobackwards commented on a diff in the pull request:

https://github.com/apache/metron/pull/588#discussion_r116581479
  
--- Diff: 
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/SquidIntegrationTest.java
 ---
@@ -29,6 +29,11 @@ String getSensorType() {
   }
 
   @Override
--- End diff --

Is this required?  Could we write a test just for testing the setting?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] metron pull request #588: METRON-954: Create ability to change output topic ...

[cestella]

GitHub user cestella opened a pull request:

https://github.com/apache/metron/pull/588

METRON-954: Create ability to change output topic of parsers from the CLI

## Contributor Comments
Right now, changing the output of the kafka topic for the parsers involves 
either adjusting source code or adjusting parser configs in zookeeper.  It 
seems sensible to add the output topic to the CLI params as a convenience 
approach.

To test this, 
* Create a topic called `my_topic` in kafka
* start up a parser topology of your choosing with `-ot my_topic`
* feed data into it
* use the console consumer to validate output is being piped into `my_topic`

## 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:
- [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:
- [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 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?
- [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?

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

 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/cestella/incubator-metron parser_output_topic

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/metron/pull/588.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 #588


commit 630727c9ce3e3deb92f21ae78742210810de0f48
Author: cstella 
Date:   2017-05-15T16:59:30Z

METRON-954: Create ability to change output topic of parsers from the CLI




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---