metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METRON-154) Decouple enrichment and indexing
Date Fri, 08 Jul 2016 18:18:11 GMT

    [ https://issues.apache.org/jira/browse/METRON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368112#comment-15368112
] 

ASF GitHub Bot commented on METRON-154:
---------------------------------------

Github user cestella commented on the issue:

    https://github.com/apache/incubator-metron/pull/185
  
    Can we please not call this METRON-154, since METRON-154 is about decoupling indexing
from enrichment and this is not that?  I do understand that this might be a prerequisite task,
but if we could create another JIRA and maybe link the two JIRAs to express the relationship.


> Decouple enrichment and indexing
> --------------------------------
>
>                 Key: METRON-154
>                 URL: https://issues.apache.org/jira/browse/METRON-154
>             Project: Metron
>          Issue Type: New Feature
>            Reporter: Ryan Merriman
>            Assignee: Nick Allen
>            Priority: Minor
>             Fix For: 0.2.2BETA
>
>
> This task involves adding another layer of abstraction between enrichment and indexing
through the use of Kafka topics.  The primary driver is the use case where a sensor is parsed
in a parser topology but doesn't necessarily need to be enriched.  This would allow parsed
sensor messages to be indexed directly without putting unnecessary load on the enrichment
topology.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message