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

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

GitHub user nickwallen opened a pull request:

    https://github.com/apache/incubator-metron/pull/185

    METRON-154 Refactor parser topology builder

    Refactored the `ParserTopologyBuilder` so that is easier to understand and 
added additional comments and documentation.
    
    I am splitting the work for METRON-154 across multiple PRs so that it is 
easier to review.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nickwallen/incubator-metron METRON-154-2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-metron/pull/185.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 #185
    
----
commit fc217a51ea5e546182b35438d264f80cf98ff136
Author: Nick Allen <[email protected]>
Date:   2016-07-08T17:01:27Z

    METRON-154 Refactor parser topology builder

----


> 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)

Reply via email to