[GitHub] metron pull request #590: METRON-953: Complete migration away from incubator...

GitHub user justinleet opened a pull request: https://github.com/apache/metron/pull/590 METRON-953: Complete migration away from incubator-metron to metron for links and docs ## Contributor Comments Moving "incubator-metron" to "metron" everywhere other than the current-book

[GitHub] metron issue #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/584 @nickwallen Yeah, that's where I landed. Looking in our pcap helper class, I see the following. ``` public static MetronEthernetDecoder createDecoder() { MetronEthernetDecoder

[GitHub] metron issue #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/584 Does `pcap_inspector` only print out for TCP packets? The first 5 of those are all UDP based (NTP & DNS). --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] metron issue #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/584 When I spin this up in full dev, half the records don't output with the pcap_inspector. I'm running: `pycapa --producer --interface eth0 --kafka-broker node1:6667 --kafka-topic pcap

Re: mvn building errors with 0.3.1

Kevin, I think your error is related to npm. Can you attach the full log file? On Mon, May 15, 2017 at 5:23 PM, Kevin Waterson wrote: > I am getting something similar.. > > [INFO] BUILD FAILURE > [INFO] >

Re: mvn building errors with 0.3.1

I am getting something similar.. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 08:08 min [INFO] Finished at: 2017-05-15T13:04:00+10:00 [INFO] Final Memory: 220M/3873M [INFO]

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116584769 --- Diff: metron-platform/metron-storm-kafka-override/src/main/java/org/apache/storm/kafka/spout/internal/Timer.java --- @@ -0,0 +1,58 @@ +/** + *

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

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

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

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

[GitHub] metron pull request #589: METRON-955: Make the default sync policy for HDFS ...

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/589#discussion_r116582720 --- Diff: metron-platform/metron-writer/src/main/java/org/apache/metron/writer/hdfs/HdfsWriter.java --- @@ -111,6 +121,16 @@ public BulkWriterResponse

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

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

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

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

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116581475 --- Diff: metron-platform/metron-storm-kafka-override/src/main/java/org/apache/storm/kafka/spout/internal/Timer.java --- @@ -0,0 +1,58 @@ +/** + *

[GitHub] metron issue #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/584 OK, works for me --- 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

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116579916 --- Diff: metron-platform/metron-storm-kafka/src/main/java/org/apache/metron/storm/kafka/flux/SimpleStormKafkaBuilder.java --- @@ -202,31 +240,4 @@ public

[GitHub] metron issue #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user cestella commented on the issue: https://github.com/apache/metron/pull/584 @mmiklavc it is. To give guarantees beyond that, would require us to shade and relocate the `metron-kafka-spout` project, which I did not want to do without some good justification. --- If your

[GitHub] metron issue #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/584 Just to clarify for others looking at this, there is a `Timer` class in `storm-kafka-client-1.1.0` which depends on a `Time` class (no 'r') in storm-core. In 1.0.3, the main version of Storm we

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116574125 --- Diff: metron-platform/metron-storm-kafka-override/src/main/java/org/apache/storm/kafka/spout/internal/Timer.java --- @@ -0,0 +1,58 @@ +/** + *

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116574075 --- Diff: metron-platform/metron-storm-kafka/src/main/java/org/apache/metron/storm/kafka/flux/SimpleStormKafkaBuilder.java --- @@ -165,13 +177,39 @@

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user justinleet commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116564604 --- Diff: metron-platform/metron-storm-kafka-override/src/main/java/org/apache/storm/kafka/spout/internal/Timer.java --- @@ -0,0 +1,58 @@ +/** +

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user justinleet commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116566613 --- Diff: metron-platform/metron-storm-kafka/src/main/java/org/apache/metron/storm/kafka/flux/SimpleStormKafkaBuilder.java --- @@ -202,31 +240,4 @@

[GitHub] metron pull request #584: METRON-950: Migrate storm-kafka-client to 1.1

Github user justinleet commented on a diff in the pull request: https://github.com/apache/metron/pull/584#discussion_r116568707 --- Diff: pom.xml --- @@ -106,7 +122,7 @@ but I justify it by noting that this should be able to be removed when we migrate to

[GitHub] metron pull request #589: METRON-955: Make the default sync policy for HDFS ...

GitHub user cestella opened a pull request: https://github.com/apache/metron/pull/589 METRON-955: Make the default sync policy for HDFS Writer be based on the batch size ## Contributor Comments Right now, we do a sync per record written in HDFS. This has performance penalties

[GitHub] metron issue #588: METRON-954: Create ability to change output topic of pars...

Github user cestella commented on the issue: https://github.com/apache/metron/pull/588 Yep, testing being a main one. YOu want to try out a parser without having it shove its data into `enrichment` --- If your project is set up for it, you can reply to this email and have your

[GitHub] metron issue #588: METRON-954: Create ability to change output topic of pars...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/588 Casey, what is the use case for this? Testing? --- 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

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

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

Re: Remember remember the 29th of April — Matt’s instructions for handling the github rename

So Apache infra confirmed that they use github’s “rename” capability, so no one needs to worry about losing connection with their remote repositories. That means that doing any of the below is strictly voluntary, and B and D (changing upstream pointers) are completely unnecessary. If you want

[GitHub] metron issue #481: METRON-322 Global Batching and Flushing

Github user mattf-horton commented on the issue: https://github.com/apache/metron/pull/481 This is simply waiting for me to have time to return to it. Would like to leave it open, if agreeable to community. --- If your project is set up for it, you can reply to this email and have

[GitHub] metron issue #425: METRON-609 Enhance Mpack to handle single-node and small-...

Github user mattf-horton commented on the issue: https://github.com/apache/metron/pull/425 Withdrawn. Much of this has been incorporated in other PRs already accepted. The remaining part is in METRON-865, formerly a sub-task of METRON-609, but now raised to a regular Bug jira

[GitHub] metron issue #408: METRON-608 Mpack to install a single-node test cluster

Github user mattf-horton commented on the issue: https://github.com/apache/metron/pull/408 Withdrawn. The current installers adequately install a single node system. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] metron pull request #408: METRON-608 Mpack to install a single-node test clu...

Github user mattf-horton closed the pull request at: https://github.com/apache/metron/pull/408 --- 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

Re: Infrastructure migrated

Thanks, Casey! -Kyle On Mon, May 15, 2017 at 10:02 AM, Otto Fowler wrote: > Thanks Casey. > > > On May 15, 2017 at 09:51:21, Casey Stella (ceste...@gmail.com) wrote: > > It appears that committers who are not PMC members did not have their > committer status migrated

Re: Infrastructure migrated

It appears that committers who are not PMC members did not have their committer status migrated over to the new repo. I have filed an INFRA ticket to correct this: https://issues.apache.org/jira/browse/INFRA-14159 I have called out certain people that I remembered. If you are not on the list in

[GitHub] metron issue #586: METRON-508 Expand Elasticsearch templates to support the ...

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/586 I updated the instructions to reflect the repo name change; hopefully it should work but I won't have a chance to test it out for a couple of days. --- If your project is set up for it, you can

Infrastructure migrated

For those who haven't noticed, the git infrastructure has migrated over. If you are a committer, you will need to adjust the URLs for the apache remote repo via: git remote set-url apache https://git-wip-us.apache.org/repos/asf/metron.git Obviously substitute "apache" for "upstream" if you

[GitHub] metron pull request #587: METRON-952 Travis CI Link in README Pointing to Ol...

Github user asfgit closed the pull request at: https://github.com/apache/metron/pull/587 --- 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

[GitHub] metron issue #587: METRON-952 Travis CI Link in README Pointing to Old Repo

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/587 I'll create a ticket and take care of it. I have a lot of this already done, while I was looking through last night. I was hoping to get a comprehensive ticket out with this change, but I'm not

[GitHub] metron issue #587: METRON-952 Travis CI Link in README Pointing to Old Repo

Github user cestella commented on the issue: https://github.com/apache/metron/pull/587 agreed; there is more to this than just this PR. --- 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

[GitHub] metron issue #587: METRON-952 Travis CI Link in README Pointing to Old Repo

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/587 I actually also noticed this last night, and was about to put in a patch until I realized there's a good amount of documentation in general that needs to point to the newer repos, and our docs

[GitHub] metron pull request #587: METRON-952 Travis CI Link in README Pointing to Ol...

GitHub user nickwallen opened a pull request: https://github.com/apache/metron/pull/587 METRON-952 Travis CI Link in README Pointing to Old Repo The Travis CI status link in the README is pointing to the old apache/incubator-metron repository. I updated this point to

Re: integration testing framework

The standard has been centos6 for installing Metron up to this point. There are some Ubuntu guides floating around as well. Jon On Mon, May 15, 2017, 8:07 AM moshe jarusalem wrote: > I would like to ask another question related to this topic. > If I am going to install metron

Re: integration testing framework

I would like to ask another question related to this topic. If I am going to install metron on a single machine (the same machine as development) which operating distribution would be best centos7 or ubuntu 16.4 or another? And is there any document to follow for such an installation ? Regards,