[jira] [Updated] (METRON-575) State from different profiles can be co-mingled incorrectly

["Casey Stella (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/METRON-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Casey Stella updated METRON-575:
--------------------------------
    Fix Version/s:     (was: Next + 1)
                   0.3.1

> State from different profiles can be co-mingled incorrectly
> -----------------------------------------------------------
>
>                 Key: METRON-575
>                 URL: https://issues.apache.org/jira/browse/METRON-575
>             Project: Metron
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>             Fix For: 0.3.1
>
>
> The ProfileBuilderBolt incorrectly assumes that it will only ever see a single [profile, entity] pair.  The bolt maintains a single StellarExecutor that is responsible for executing the init, update, result expressions.  This assumption is incorrect as Storm's field grouping only guarantees that the same profile/entity pairs will go to the same task.  Storm does not guarantee that a task only receives a single profile/entity pair.
> The easiest fix is to maintain a cache that maps a profile/entity to its state.  This would follow what is currently done in the Join bolt. 



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