[
https://issues.apache.org/jira/browse/METRON-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677241#comment-15677241
]
ASF GitHub Bot commented on METRON-575:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/362
I would recommend using ordinary time units (seconds, minutes, hours, days)
rather than a number of periods, for the TTL. This puts the lifetime info in
one place instead of two, and prevents questions like "I changed the period,
does the TTL change too?"
> 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)
