[
https://issues.apache.org/jira/browse/METRON-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881571#comment-15881571
]
ASF GitHub Bot commented on METRON-694:
---------------------------------------
Github user JonZeolla commented on the issue:
https://github.com/apache/incubator-metron/pull/453
I'm sorry if this was already covered and I missed it, I'm writing this
from my phone. How does this handle errors during indexing itself? For
instance, if the failure is due to the content of a specific field and that is
placed in rawMessage/raw_message, wouldn't we have a failure loop? I was under
the assumption that rawMessage/raw_message was not going to be included because
of this sort of cyclical concern. Just wanted to double check on that because
I've definitely seen those sort of failures in my environment.
This also may be mitigated by the outcome of the ongoing dev list
conversation "[DISCUSS] Management of Elastic and other index schemas" because
we could attempt to fix those known sort of issues in the abstraction, but it
still leaves us open to unknown issues.
> Index Errors from Topologies
> ----------------------------
>
> Key: METRON-694
> URL: https://issues.apache.org/jira/browse/METRON-694
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
>
> Need to make sure (and review) that all the bolts write into the error queue.
> Errors should then be consumed from the error queue and indexed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
