[
https://issues.apache.org/jira/browse/METRON-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890741#comment-15890741
]
ASF GitHub Bot commented on METRON-694:
---------------------------------------
Github user JonZeolla commented on the issue:
https://github.com/apache/incubator-metron/pull/453
> For the concern about indexing errors getting in a loop, I thought of a
simple solution that required no extra work. If an error happens in the
indexing topology, simply send it to a different error topic. Would this be
acceptable? I wanted to throw this out there before implementing custom logic
in the indexing topology classes.
Hmm, that seems like it would be somewhat confusing to me. Unless I'm
missing something, that error would just not show up in the "typical"
topic/dashboard. How about if there's an error during indexing, retry with
more bare-bones data and adding a k/v pair that indicates such?
> 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)
