[
https://issues.apache.org/jira/browse/STREAMS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190359#comment-14190359
]
ASF GitHub Bot commented on STREAMS-206:
----------------------------------------
GitHub user steveblackmon opened a pull request:
https://github.com/apache/incubator-streams/pull/117
resolves STREAMS-206, pending feedback
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-streams STREAMS-206
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-streams/pull/117.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #117
----
commit 1ee614e77d8fa16cc58aec689d5d7716a8e29026
Author: sblackmon <[email protected]>
Date: 2014-10-30T16:48:15Z
resolves STREAMS-206, pending feedback
----
> 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)
