You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by "Steve Blackmon (JIRA)" <ji...@apache.org> on 2014/11/03 17:40:34 UTC
[jira] [Resolved] (STREAMS-206) Additional control over ESWriter
tag lifecycle
[ https://issues.apache.org/jira/browse/STREAMS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Blackmon resolved STREAMS-206.
------------------------------------
Resolution: Fixed
merged
> Additional control over ESWriter tag lifecycle
> ----------------------------------------------
>
> Key: STREAMS-206
> URL: https://issues.apache.org/jira/browse/STREAMS-206
> Project: Streams
> Issue Type: Improvement
> Reporter: Steve Blackmon
> Assignee: Steve Blackmon
>
> PercolateTagProcessor sets up tagging rules upon startup, and remove them upon shutdown. There may be cases where this is not the desired behavior. For example, if three streams are concurrently writing and tagging to the same index, after stream 1 completes neither stream 2 or 3 are able to tag because stream 1 deletes the tags.
> Update code to retain same default behavior but provide more flexibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)