You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/10/09 09:06:26 UTC

[jira] [Resolved] (STORM-1094) kafka offset does not advance when deserializer yields no object

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

Jungtaek Lim resolved STORM-1094.
---------------------------------
       Resolution: Fixed
         Assignee: Pete Prokopowicz
    Fix Version/s: 0.10.0

Thanks [~prokopowicz],
I merged this into master and 0.10.x-branch.

> kafka offset does not advance when deserializer yields no object 
> -----------------------------------------------------------------
>
>                 Key: STORM-1094
>                 URL: https://issues.apache.org/jira/browse/STORM-1094
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 0.10.0, 0.11.0, 0.9.6
>            Reporter: Pete Prokopowicz
>            Assignee: Pete Prokopowicz
>              Labels: patch
>             Fix For: 0.10.0
>
>
> If a custom deserializer returns an empty list of objects as a result of deserializing messages from kafka, the partition manager does not advance the kafka offset, and the same message will continue to be deserialized and return nothing.  The code works if the deserializer returns null, but not if it returns an empty list.



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