flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLUME-3031) sequence source should reset its counter for event body on channel exception
Date Tue, 22 Nov 2016 18:36:59 GMT

    [ https://issues.apache.org/jira/browse/FLUME-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687513#comment-15687513
] 

ASF GitHub Bot commented on FLUME-3031:
---------------------------------------

GitHub user satiatcloudera opened a pull request:

    https://github.com/apache/flume/pull/90

    FLUME-3031: sequence source should reset its counter for event body on channel exception

    added code fix for event body generation
    updated user guide
    reworked testing: removed original tests and introduced three new one to extend coverage

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/satiatcloudera/flume sequencesource

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flume/pull/90.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 #90
    
----

----


> sequence source should reset its counter for event body on channel exception
> ----------------------------------------------------------------------------
>
>                 Key: FLUME-3031
>                 URL: https://issues.apache.org/jira/browse/FLUME-3031
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources, Test
>    Affects Versions: v1.7.0
>            Reporter: Attila Simon
>            Assignee: Attila Simon
>
> SequenceGeneratorSource uses a counter to construct the body of the generated Events
which counter is not reseted when writing event to channel failed. This can lead to a situation
that the total number of unique events at destination (if deduplication relies on msg body)
is bigger than the totalEvents configuration parameter due to the retries.
> Fix should make sure that number of events at destination after filtering out the duplicates
is equal to the configured value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message