[
https://issues.apache.org/jira/browse/METRON-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687592#comment-15687592
]
ASF GitHub Bot commented on METRON-575:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/362
+1 stands
On Tue, Nov 22, 2016 at 14:07 Nick Allen <[email protected]> wrote:
> Everything is working in Quick Dev with this change.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/incubator-metron/pull/362#issuecomment-262334561>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AAg-x5Dyp-hrtwdOBji7RMJ0At3S766yks5rAz14gaJpZM4K2kyK>
> .
>
> 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
> Reporter: Nick Allen
> Assignee: Nick Allen
>
> 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)
