Re: DISCUSS: Quick change to parser config

I’m not sure about consensus. I would like to see it summarized. My point about assignment has to do with how many assignment like operators we are going to support. The fact that the assignment is to a variable that is temporary or not doesn’t need to be part of the grammar/language, since all

[GitHub] metron issue #851: METRON-1336 Patching Can Result in Bad Configuration

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/851 @mmiklavc @cestella The kick is complete. All PRs merged. Ready for review. ---

[GitHub] metron issue #840: METRON-939: Upgrade ElasticSearch and Kibana

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/840 Ok, here is the remaining bit of the test plan for verifying ES. Thanks @cestella for pulling together some of the public test scripts around this. # Test Script Testing Kibana

[GitHub] metron issue #840: METRON-939: Upgrade ElasticSearch and Kibana

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/840 So, this has me thinking It is a shame to have these test materials ( and others like @JonZeolla creates ) embedded in these pr's. Maybe we should have someplace to put them in

Re: DISCUSS: Quick change to parser config

Personally I suspect that temporary variable is a different thing as is the assignment PR. Might be useful for intermediate steps in a parser, but then we’re potentially getting more complex than a parser wants to be. I am warming to the idea of temporary variables though. In terms of the

[GitHub] metron pull request #855: METRON-1338 Excluding retry files from RAT check

Github user asfgit closed the pull request at: https://github.com/apache/metron/pull/855 ---

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154763112 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -572,15 +590,22 @@

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154761355 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -343,25 +343,42 @@

Re: [DISCUSS] Upcoming Release

Can we resolve the conversation regarding the second repo? I was waiting to get more input/preferences from people There's also a documentation update that fixes a few broken Stellar docs that already has aa +1, I just need to merge it. Jon On Mon, Dec 4, 2017, 17:01 Casey Stella

Re: Heterogeneous indexing batch size for different Metron feeds

My first thought is what are the errors when you get a high error rate? On December 4, 2017 at 19:34:29, Ali Nazemian (alinazem...@gmail.com) wrote: Any thoughts? On Sun, Dec 3, 2017 at 11:27 PM, Ali Nazemian wrote: > Hi, > > We have noticed recently that no matter

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user nickwallen commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154821946 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -343,25 +343,42 @@ public

Re: [DISCUSS] Upcoming Release

I would be in favor of a release at this point. On Mon, Dec 4, 2017 at 4:57 PM, Matt Foley wrote: > Hey all, > I see METRON-1252 was resolved over the weekend. Shall I go ahead and > start the process with 0.4.2 release? > Does anyone have any commits they feel strongly

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user nickwallen commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154799152 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -572,15 +590,22 @@ public

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154804149 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -572,15 +590,22 @@

[GitHub] metron issue #840: METRON-939: Upgrade ElasticSearch and Kibana

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/840 I don't think that's a bad idea. I definitely like having test scripts associated with the PR's because we can explicitly see what was done and/or recommended at the time the PR was being ushered

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154803527 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -572,15 +590,22 @@

Re: Heterogeneous indexing batch size for different Metron feeds

Any thoughts? On Sun, Dec 3, 2017 at 11:27 PM, Ali Nazemian wrote: > Hi, > > We have noticed recently that no matter what batch size we use for Metron > indexing feeds, as long as we start using different batch size for > different Metron feeds, indexing topology

[GitHub] metron issue #840: METRON-939: Upgrade ElasticSearch and Kibana

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/840 Yeah, I'm trying to think of the right way to do it, without having to have it be "officially maintained". more like an informal /testing_stuff , with some descriptions, when it was

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

Okay, looking at this from the perspective of making a release: We have two choices: a) I can simply make a 0.1 (or 1.0 or 0.4.2) release of metron-bro-plugin-kafka, at the same time and using the same process (modulo the necessary) as Metron.  This is dirt simple.  b) I or someone needs

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user nickwallen commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154798328 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -343,25 +343,42 @@ public

Re: [DISCUSS] Upcoming Release

Hey all, I see METRON-1252 was resolved over the weekend. Shall I go ahead and start the process with 0.4.2 release? Does anyone have any commits they feel strongly should go in before 0.4.2 is done, or are we ready to call it good? I believe there is consensus the 0.4.2 release should

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

I would prefer a, but I was initially thinking of doing the plugin first and then get in the two PRs out to use this new tag, which are already +1'd and just waiting on this conversation. For reference, https://github.com/apache/metron/pull/847 and

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

Honestly, I think (a) is sufficient, and less work. But I’m willing to do (b) if the community prefers. On 12/4/17, 5:54 PM, "Otto Fowler" wrote: It seems to me, as I believe I have stated before that a) feels like the proper way to handle this. It is how I

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154824031 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -343,25 +343,42 @@

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154824244 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -343,25 +343,42 @@

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

It seems to me, as I believe I have stated before that a) feels like the proper way to handle this. It is how I have seen other projects like NiFi handle things as well. On December 4, 2017 at 17:14:41, Matt Foley (ma...@apache.org) wrote: Okay, looking at this from the perspective of making

Re: Heterogeneous indexing batch size for different Metron feeds

No specific error in the logs. I haven't enabled debug/trace, though. On Tue, Dec 5, 2017 at 11:54 AM, Otto Fowler wrote: > My first thought is what are the errors when you get a high error rate? > > > On December 4, 2017 at 19:34:29, Ali Nazemian

[GitHub] metron issue #850: METRON-1335: Install metron-maas-service RPM as a part of...

Github user anandsubbu commented on the issue: https://github.com/apache/metron/pull/850 bump. Any feedback on this pull request? ---

Re: DISCUSS: Quick change to parser config

So, just chiming in here. It seems to me that we have a problem with extraneous fields in a couple of different ways: * Temporary Variables I think that the problem of temporary variables is one beyond just the parser. What I'd like to see is the Stellar field transformations operate similar

Re: DISCUSS: Quick change to parser config

Would https://github.com/apache/metron/pull/687 play some role in this? Or could it be made to? On December 4, 2017 at 12:21:40, Casey Stella (ceste...@gmail.com) wrote: So, just chiming in here. It seems to me that we have a problem with extraneous fields in a couple of different ways: *

[GitHub] metron issue #856: METRON-1339 Stellar Shell functionality to verify stored ...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/856 @cestella @simonellistonball With the new implementation, doing the blob or file check should be a piece of cake would you prefer it as part of this or as a new issue? ---

[GitHub] metron pull request #851: METRON-1336 Patching Can Result in Bad Configurati...

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/851#discussion_r154663544 --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/ConfigurationsUtils.java --- @@ -343,25 +343,57 @@ public

[GitHub] metron issue #857: METRON-1340: Improve e2e tests for metron alerts

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/857 I haven't looked at the code yet, but I was able to pull this down and run the e2e tests repeatedly without failures, so this is definitely great stuff. ---

[GitHub] metron issue #823: METRON-1286 Add MIN & MAX Stellar functions

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/823 +1, I'm set ---

[GitHub] metron pull request #823: METRON-1286 Add MIN & MAX Stellar functions

Github user asfgit closed the pull request at: https://github.com/apache/metron/pull/823 ---