You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "Stig Rohde Døssing (JIRA)" <ji...@apache.org> on 2018/12/14 15:57:00 UTC

[jira] [Resolved] (STORM-2990) Make the storm-kafka-client Trident spout FirstPollOffsetStrategy behavior consistent with the regular spout

     [ https://issues.apache.org/jira/browse/STORM-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stig Rohde Døssing resolved STORM-2990.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

> Make the storm-kafka-client Trident spout FirstPollOffsetStrategy behavior consistent with the regular spout
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-2990
>                 URL: https://issues.apache.org/jira/browse/STORM-2990
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-kafka-client
>    Affects Versions: 2.0.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> The EARLIEST and LATEST semantics were changed in the regular spout so the spout only starts over when the topology is redeployed. The Trident spout should behave the same way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)