GitHub user srdo opened a pull request:

    https://github.com/apache/storm/pull/2307

    STORM-2546: Fix storm-kafka-client spout getting stuck when retriable 
offsets were deleted from the Kafka log due to topic compaction

    This requires the changes in https://github.com/apache/storm/pull/2156 for 
correctness, please ignore the first commit.
    
    Here's the idea behind these changes 
https://issues.apache.org/jira/browse/STORM-2546?focusedCommentId=16151172&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16151172
    
    KafkaSpoutCommitTest was renamed, so the first test in 
KafkaSpoutLogCompactionSupportTest was already there and can be skipped.

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

    $ git pull https://github.com/srdo/storm STORM-2546

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

    https://github.com/apache/storm/pull/2307.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 #2307
    
----
commit 5d13d3a1142d808107e630479514a922904f2187
Author: Stig Rohde Døssing <stigdoess...@gmail.com>
Date:   2017-06-10T17:38:22Z

    STORM-2549: Fix broken enforcement mechanism for maxUncommittedOffsets in 
storm-kafka-client spout

commit 19a6c4e8824bbf1c98d36e4073e68631ece9047b
Author: Stig Rohde Døssing <s...@apache.org>
Date:   2017-09-02T21:50:33Z

    STORM-2546: Fix storm-kafka-client spout getting stuck when retriable 
tuples were deleted from the Kafka log due to topic compaction

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to