[
https://issues.apache.org/jira/browse/STREAMS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192449#comment-14192449
]
ASF GitHub Bot commented on STREAMS-206:
----------------------------------------
Github user rbnks commented on the pull request:
https://github.com/apache/incubator-streams/pull/117#issuecomment-61327326
So this basically allows you to optional load new percolate rules and
remove them afterwords, instead of the delete->load->delete process being
automatic?
> 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)
