[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686414#comment-16686414
]
ASF GitHub Bot commented on METRON-1815:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1249
I'm ok with changing parsing to something else, just not parsers.
---
[
https://issues.apache.org/jira/browse/METRON-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686560#comment-16686560
]
ASF GitHub Bot commented on METRON-1827:
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686603#comment-16686603
]
ASF GitHub Bot commented on METRON-1868:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686606#comment-16686606
]
ASF GitHub Bot commented on METRON-1860:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@nickwallen I did not think of that. I was improving the process that
stands today. I think in a world where the posted image exists, we would still
want the ability to try the latest ( to
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686649#comment-16686649
]
ASF GitHub Bot commented on METRON-1860:
Github user nickwallen commented on the issue:
Nick Allen created METRON-1871:
--
Summary: Cannot Run Elasticsearch Integration Tests in IDE
Key: METRON-1871
URL: https://issues.apache.org/jira/browse/METRON-1871
Project: Metron
Issue Type:
[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686668#comment-16686668
]
ASF GitHub Bot commented on METRON-1815:
Github user ottobackwards commented on the issue:
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/1261
I'm going to take a stab at a further look next week. For now I gave it a
quick run-up and it was successful.
---
GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/1262
METRON-1871 Cannot Run Elasticsearch Integration Tests in IDE
There are some log4j dependencies in the metron-elasticsearch that cause
problems when attempting to run the Elasticsearch
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686670#comment-16686670
]
ASF GitHub Bot commented on METRON-1860:
Github user JonZeolla commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1249
@justinleet I'm fine with that
---
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686653#comment-16686653
]
ASF GitHub Bot commented on METRON-1860:
Github user nickwallen commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@mmiklavc That is basically correct. Except that the ansible version is
2.5, since it only applies to this build, and allows for the yaml log
formatting.
Also, in the latest
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686625#comment-16686625
]
ASF GitHub Bot commented on METRON-1868:
Github user JonZeolla commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686631#comment-16686631
]
ASF GitHub Bot commented on METRON-1868:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686616#comment-16686616
]
ASF GitHub Bot commented on METRON-1860:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686642#comment-16686642
]
ASF GitHub Bot commented on METRON-1815:
Github user justinleet commented on the issue:
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1249
It's a bit inelegant, but what if we do something like:
```
âââ metron-parsing
âââ metron-parsers
âââ metron-parsers-common
âââ
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1249
I don't want to bog this down too much. I'm good with either the recent rev
you proposed or simply adding the appropriate notes in the pom internals and
dev docs. Chefs choice.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
@nickwallen That is an option, but not something I would pick as the goal
from the outset if you know what I mean.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
anyone have any ideas of the best way to time these things?
---
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686693#comment-16686693
]
ASF GitHub Bot commented on METRON-1860:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686696#comment-16686696
]
ASF GitHub Bot commented on METRON-1860:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686691#comment-16686691
]
ASF GitHub Bot commented on METRON-1868:
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/METRON-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686690#comment-16686690
]
ASF GitHub Bot commented on METRON-1871:
Github user merrimanr commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686618#comment-16686618
]
ASF GitHub Bot commented on METRON-1860:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1260
+1, sorry I missed this
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1261
If we go this approach, why not just replace the existing "Full Dev"
environments (both centos and ubuntu) rather than add new environments to
support, test, and keep in-sync?
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1262
I find myself commenting these out every time I run ES integration tests in
my IDE. +1
---
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686683#comment-16686683
]
ASF GitHub Bot commented on METRON-1860:
Github user ottobackwards commented on the issue:
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/1260
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1261
We could also use more tags, for example I may want to skip building the
java, but not skip building the RPMs. Think of a dev flow -> I make my change,
run my local tests and want to spin up
[
https://issues.apache.org/jira/browse/METRON-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Allen updated METRON-1871:
---
Attachment: Screen Shot 2018-11-14 at 10.26.18 AM.png
> Cannot Run Elasticsearch Integration Tests
[
https://issues.apache.org/jira/browse/METRON-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686672#comment-16686672
]
ASF GitHub Bot commented on METRON-1871:
GitHub user nickwallen opened a pull request:
GitHub user merrimanr opened a pull request:
https://github.com/apache/metron/pull/1263
METRON-1870: Intermittent Stellar REST test failures
## Contributor Comments
This PR attempts to fix the intermittent test failures reported in the Jira.
For this failure:
```
GitHub user justinleet opened a pull request:
https://github.com/apache/metron/pull/1264
METRON-1872: Move rat plugin away from snapshot version
## Contributor Comments
Removes the Apache dev snapshot plugin repo, and bumps the rat version to
0.13 instead of 0.13-SNAPSHOT
[
https://issues.apache.org/jira/browse/METRON-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686829#comment-16686829
]
ASF GitHub Bot commented on METRON-1872:
GitHub user justinleet opened a pull request:
[
https://issues.apache.org/jira/browse/METRON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686826#comment-16686826
]
ASF GitHub Bot commented on METRON-1870:
GitHub user merrimanr opened a pull request:
Justin Leet created METRON-1872:
---
Summary: Move rat plugin away from snapshot version
Key: METRON-1872
URL: https://issues.apache.org/jira/browse/METRON-1872
Project: Metron
Issue Type:
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1242
I'm about to merge this and wanted to give some added feedback. @anandsubbu
and I made some additional changes to the tuning options, specifically setting
`topology.ackers.executors` equal to the
[
https://issues.apache.org/jira/browse/METRON-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686861#comment-16686861
]
ASF GitHub Bot commented on METRON-1834:
Github user mmiklavc commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1263
+1 pending successful Travis run. Thanks
---
[
https://issues.apache.org/jira/browse/METRON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686860#comment-16686860
]
ASF GitHub Bot commented on METRON-1870:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687053#comment-16687053
]
ASF GitHub Bot commented on METRON-1749:
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/1217
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/857
I also requested that this be closed in this ticket;
https://issues.apache.org/jira/browse/INFRA-17251
---
[
https://issues.apache.org/jira/browse/METRON-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687059#comment-16687059
]
ASF GitHub Bot commented on METRON-1340:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686930#comment-16686930
]
ASF GitHub Bot commented on METRON-1870:
Github user asfgit closed the pull request at:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1264
+1 Thanks @justinleet
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1197
@JonZeolla That error is a pre-existing condition that is tracked here;[
METRON-1810](https://issues.apache.org/jira/browse/METRON-1810). I am not sure
what the root cause is.
---
[
https://issues.apache.org/jira/browse/METRON-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686957#comment-16686957
]
ASF GitHub Bot commented on METRON-1778:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686958#comment-16686958
]
ASF GitHub Bot commented on METRON-1762:
Github user merrimanr closed the pull request at:
GitHub user dopheide-esnet opened a pull request:
https://github.com/apache/metron-bro-plugin-kafka/pull/18
Remove version from show-plugin btest output in prep for Bro 2.7
## Contributor Comments
Update show-plugin.bro test to remove the version number from the baseline
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1242
Ship it!
---
[
https://issues.apache.org/jira/browse/METRON-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686950#comment-16686950
]
ASF GitHub Bot commented on METRON-1825:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686949#comment-16686949
]
ASF GitHub Bot commented on METRON-1872:
Github user nickwallen commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1237
Have you spun this up in Full Dev and tested?
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/526
I opened a ticket to get this closed;
https://issues.apache.org/jira/browse/INFRA-17251
---
[
https://issues.apache.org/jira/browse/METRON-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687123#comment-16687123
]
ASF GitHub Bot commented on METRON-1340:
Github user gmcdonald closed the pull request at:
Github user gmcdonald closed the pull request at:
https://github.com/apache/metron/pull/857
---
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/1237
Yup, that was actually how I found METRON-1826 was an issue. Sorry, I
should have noted that.
---
[
https://issues.apache.org/jira/browse/METRON-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687143#comment-16687143
]
ASF GitHub Bot commented on METRON-1825:
Github user JonZeolla commented on the issue:
64 matches
Mail list logo
