streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (STREAMS-206) Additional control over ESWriter tag lifecycle
Date Fri, 31 Oct 2014 20:39:34 GMT


ASF GitHub Bot commented on STREAMS-206:

Github user steveblackmon commented on the pull request:
    All tags defined in the config will be loaded no matter - this patch makes deletion before
and after optional.
    > On Oct 31, 2014, at 3:36 PM, Ryan Ebanks <> wrote:
    > So this basically allows you to optional load new percolate rules and remove them
afterwords, instead of the delete->load->delete process being automatic?
    > —
    > Reply to this email directly or view it on GitHub <>.

> Additional control over ESWriter tag lifecycle
> ----------------------------------------------
>                 Key: STREAMS-206
>                 URL:
>             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

View raw message