[
https://issues.apache.org/jira/browse/METRON-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325135#comment-15325135
]
ASF GitHub Bot commented on METRON-217:
---------------------------------------
GitHub user cestella opened a pull request:
https://github.com/apache/incubator-metron/pull/149
METRON-217: Found a grabbag of bugs
Doing some scale testing, I found a grabbag of bugs:
* The elasticsearch writer should allow multiple ES hosts to be passed in
via a List. This should be backwards compatible.
* There is a concurrent modification exception while cloning the message
field
* The parser topology numSpoutTasks and numParserTasks are swapped
* The grok parser should throw an exception if it cannot parse so the
message that could not be parsed is sent to the error queue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cestella/incubator-metron bug_squash_1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/149.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 #149
----
commit 3738df5112bf7514fb1a9e9b6c7d812ce97a8a69
Author: cstella <[email protected]>
Date: 2016-06-10T19:17:57Z
Fixing a grabbag of bugs.
commit 08609a91483683c241e7f3e706630f79e25bffcb
Author: cstella <[email protected]>
Date: 2016-06-10T19:28:11Z
Updating writer bolt.
----
> Found a grabbag of bugs
> -----------------------
>
> Key: METRON-217
> URL: https://issues.apache.org/jira/browse/METRON-217
> Project: Metron
> Issue Type: Bug
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> Doing some scale testing, I found a grabbag of bugs:
> * The elasticsearch writer should allow multiple ES hosts to be passed in via
> a List. This should be backwards compatible.
> * There is a concurrent modification exception while cloning the message field
> * The parser topology numSpoutTasks and numParserTasks are swapped
> * The grok parser should throw an exception if it cannot parse so the message
> that could not be parsed is sent to the error queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
