[
https://issues.apache.org/jira/browse/METRON-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525783#comment-16525783
]
ASF GitHub Bot commented on METRON-1646:
GitHub user nickwallen opened a pull request:
GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/1087
METRON-1646 Sensor Stubs should work when kerberized
The sensor-stubs do not work in a kerberized development environment. This
makes it difficult to test issues related to kerberization.
Nick Allen created METRON-1646:
--
Summary: Sensor Stubs should work when kerberized
Key: METRON-1646
URL: https://issues.apache.org/jira/browse/METRON-1646
Project: Metron
Issue Type:
[
https://issues.apache.org/jira/browse/METRON-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525735#comment-16525735
]
ASF GitHub Bot commented on METRON-1645:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525685#comment-16525685
]
ASF GitHub Bot commented on METRON-1641:
Github user mmiklavc commented on the issue:
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1081
Heads up, hadoop config class is where you set queue name iirc. We already
pass that in as an arg. This would simply need to be provided via the calling
job manager class.
[
https://issues.apache.org/jira/browse/METRON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525642#comment-16525642
]
ASF GitHub Bot commented on METRON-1644:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1084
@ottobackwards Ok, let me know what you think about
[this](https://github.com/cestella/incubator-metron/blob/enveloped_message_supplier/metron-platform/metron-parsers/ParserChaining.md).
Is it
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525626#comment-16525626
]
ASF GitHub Bot commented on METRON-1641:
Github user mmiklavc commented on the issue:
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1081
Also @merrimanr agreed about the points you made regarding restart-ability,
etc. in the long run. In the short term, @cestella has done a rather good job
of summarizing my thoughts on a v1 pass at
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525617#comment-16525617
]
ASF GitHub Bot commented on METRON-1641:
Github user mmiklavc commented on the issue:
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1081
Good catch on the FS @merrimanr - also finding that via manual testing. I
believe I have a workaround that degrades nicely to the configuration default
and also allows you to pass in the scheme in
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1079
I tested this in full dev and group requests are correctly being sent with
the score field when 1 group is selected. +1
---
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525593#comment-16525593
]
ASF GitHub Bot commented on METRON-1641:
Github user merrimanr commented on the issue:
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1081
I spun this up in full dev, ran a fixed query, and got this error:
```
Exception in thread "main" java.lang.IllegalArgumentException: Wrong FS:
file://./, expected: hdfs://node1:8020
[
https://issues.apache.org/jira/browse/METRON-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525486#comment-16525486
]
ASF GitHub Bot commented on METRON-1645:
Github user nickwallen commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1086
Looks like we're having problems kerberizing after we merged the Solr
feature branch. . I will run this up now and validate your fix. Good find
@MohanDV !
---
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525270#comment-16525270
]
ASF GitHub Bot commented on METRON-1641:
Github user merrimanr commented on the issue:
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1081
Perfect. That addresses my concern. Doing this in a follow on is fine
since it's not necessary when using the CLI.
---
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525262#comment-16525262
]
ASF GitHub Bot commented on METRON-1641:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1081
One more comment about restartability, I think we could potentially support
this with this architecture in the future. You can recover the Job object from
MR via the JobClient
```
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525252#comment-16525252
]
ASF GitHub Bot commented on METRON-1641:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1081
One thing I didn't see. Can we make sure we pass along the yarn queue to
the job?
---
GitHub user MohanDV opened a pull request:
https://github.com/apache/metron/pull/1086
METRON-1645: Check wether the Solr management pack is installed before
configuring the solr principal name.
## Contributor Comments
Check wether the Solr management pack is installed
[
https://issues.apache.org/jira/browse/METRON-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525245#comment-16525245
]
ASF GitHub Bot commented on METRON-1645:
GitHub user MohanDV opened a pull request:
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525244#comment-16525244
]
ASF GitHub Bot commented on METRON-1641:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1081
I think for a first cut, it's ok to have the restrictions that:
* the REST API controls only the jobs it creates. Otherwise, we would need
more refactoring in the CLI to drop the output in the
[
https://issues.apache.org/jira/browse/METRON-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525235#comment-16525235
]
ASF GitHub Bot commented on METRON-1636:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1085
Hey, thanks for the contribution! Can you make the title METRON-1636: Fix
broken unit test setup in metron-alerts? Also, if you could mark the boxes in
the pull request checklist to let us know
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525232#comment-16525232
]
ASF GitHub Bot commented on METRON-1641:
Github user merrimanr commented on the issue:
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1081
Looks good! One thing I'm trying to wrap my head around is how we get
status if we only have a job id or unique identifier for a job? JobStatus
doesn't have an id so I'm assuming resultPath is
Mohan created METRON-1645:
-
Summary: All the Metron Service stop/start fail after Kerberizing
the cluster due to missing config parameters
Key: METRON-1645
URL: https://issues.apache.org/jira/browse/METRON-1645
GitHub user tiborm opened a pull request:
https://github.com/apache/metron/pull/1085
Metron 1636
I made changes in the unit tests of the metron-alert UI to make test
runnable.
I also removed Router from table-view.component and tree-view.component
because it was just
[
https://issues.apache.org/jira/browse/METRON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525204#comment-16525204
]
ASF GitHub Bot commented on METRON-1644:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1084
@ottobackwards Yeah, that is a really good point. I'll write up something.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1084
Yes. The use case is useful, but this is more dev. focused, if that makes
sense.
---
[
https://issues.apache.org/jira/browse/METRON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525201#comment-16525201
]
ASF GitHub Bot commented on METRON-1644:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525199#comment-16525199
]
ASF GitHub Bot commented on METRON-1643:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1083
@ottobackwards Makes sense; I made the change and percolated it to
METRON-1644 aka #1084
---
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525194#comment-16525194
]
ASF GitHub Bot commented on METRON-1643:
Github user ottobackwards commented on a diff in the
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/1083#discussion_r198536558
--- Diff: metron-platform/metron-parsers/README.md ---
@@ -337,6 +337,28 @@ The following config will rename the fields
`old_field` and
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525192#comment-16525192
]
ASF GitHub Bot commented on METRON-1643:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1083
+1 to SELECT
What you are saying is SET FIELD to X if SELECT.
It would be SWITCH if it were a different X per matching regex
---
[
https://issues.apache.org/jira/browse/METRON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525191#comment-16525191
]
ASF GitHub Bot commented on METRON-1644:
Github user cestella commented on the issue:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1084
Yeah, I tend to agree @ottobackwards . There is a high level diagram in
the use-case under the "High Level Solution" section; do you think that should
be extracted out into its own document along
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525188#comment-16525188
]
ASF GitHub Bot commented on METRON-1641:
Github user mmiklavc commented on a diff in the pull
Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/1081#discussion_r198533881
--- Diff: metron-platform/pom.xml ---
@@ -46,6 +46,7 @@
metron-enrichment
metron-solr
metron-parsers
+
[
https://issues.apache.org/jira/browse/METRON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525186#comment-16525186
]
ASF GitHub Bot commented on METRON-1644:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1084
This is significant enough that I think some level of design write-up is
warranted. At some point we'll want to update the top level doc's and
diagrams, but I'm OK with that being a follow
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1083
@ottobackwards Yeah, my history of really crappy naming continues. How
about `REGEX_SELECT` or `REGEX_SWITCH`?
---
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525185#comment-16525185
]
ASF GitHub Bot commented on METRON-1643:
Github user cestella commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525183#comment-16525183
]
ASF GitHub Bot commented on METRON-1643:
Github user cestella commented on a diff in the pull
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/1083#discussion_r198530993
--- Diff: metron-platform/metron-parsers/README.md ---
@@ -337,6 +337,28 @@ The following config will rename the fields
`old_field` and
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525181#comment-16525181
]
ASF GitHub Bot commented on METRON-1643:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1083
I am not sure ROUTING is a good name for this. This is more like a SELECT.
---
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525179#comment-16525179
]
ASF GitHub Bot commented on METRON-1643:
Github user ottobackwards commented on a diff in the
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/1083#discussion_r198530068
--- Diff: metron-platform/metron-parsers/README.md ---
@@ -337,6 +337,28 @@ The following config will rename the fields
`old_field` and
[
https://issues.apache.org/jira/browse/METRON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525162#comment-16525162
]
ASF GitHub Bot commented on METRON-1644:
GitHub user cestella opened a pull request:
Casey Stella created METRON-1644:
Summary: Support parser chaining
Key: METRON-1644
URL: https://issues.apache.org/jira/browse/METRON-1644
Project: Metron
Issue Type: Improvement
GitHub user cestella opened a pull request:
https://github.com/apache/metron/pull/1084
METRON-1644: Support parser chaining
## Contributor Comments
Currently we have only one layer of parsing prior to enrichment, but often
real data is more complex. For instance, often data is
[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525154#comment-16525154
]
ASF GitHub Bot commented on METRON-1643:
GitHub user cestella opened a pull request:
GitHub user cestella opened a pull request:
https://github.com/apache/metron/pull/1083
METRON-1643: Create a REGEX_ROUTING field transformation
## Contributor Comments
A relatively common pattern is to choose the value of a field based on if
another field matches a set of
Casey Stella created METRON-1643:
Summary: Create a REGEX_ROUTING field transformation
Key: METRON-1643
URL: https://issues.apache.org/jira/browse/METRON-1643
Project: Metron
Issue Type:
[
https://issues.apache.org/jira/browse/METRON-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525149#comment-16525149
]
ASF GitHub Bot commented on METRON-1642:
GitHub user cestella opened a pull request:
GitHub user cestella opened a pull request:
https://github.com/apache/metron/pull/1082
METRON-1642: KafkaWriter should be able choose the topic from a field in
addition to topology construction time
## Contributor Comments
Currently, we choose the kafka topic via the
Casey Stella created METRON-1642:
Summary: KafkaWriter should be able choose the topic from a field
in addition to topology construction time
Key: METRON-1642
URL:
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525119#comment-16525119
]
ASF GitHub Bot commented on METRON-1641:
Github user cestella commented on a diff in the pull
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/1081#discussion_r198503437
--- Diff: metron-platform/pom.xml ---
@@ -46,6 +46,7 @@
metron-enrichment
metron-solr
metron-parsers
+
[
https://issues.apache.org/jira/browse/METRON-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525108#comment-16525108
]
ASF GitHub Bot commented on METRON-1619:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1064
+1 by inspection
---
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524637#comment-16524637
]
ASF GitHub Bot commented on METRON-1641:
Github user mmiklavc commented on the issue:
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1081
**Testing**
Get PCAP data into Metron:
1. Install and setup pycapa - look for "Install pycapa" here
[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524627#comment-16524627
]
ASF GitHub Bot commented on METRON-1641:
GitHub user mmiklavc opened a pull request:
GitHub user mmiklavc opened a pull request:
https://github.com/apache/metron/pull/1081
METRON-1641: Enable Pcap jobs to be submitted asynchronously
## Contributor Comments
https://issues.apache.org/jira/browse/METRON-1641
This enables Pcap Jobs to be run
Michael Miklavcic created METRON-1641:
-
Summary: Enable Pcap jobs to be submitted asynchronously
Key: METRON-1641
URL: https://issues.apache.org/jira/browse/METRON-1641
Project: Metron
75 matches
Mail list logo
