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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on STORM-1094:
---------------------------------------

Github user prokopowicz commented on the pull request:

    https://github.com/apache/storm/pull/758#issuecomment-146227524
  
    I issued this JIRA regarding the bug:
    
    https://issues.apache.org/jira/browse/STORM-1094
    
    
    On Tue, Oct 6, 2015 at 3:40 PM, Jungtaek Lim <no...@github.com>
    wrote:
    
    > +1, too.
    > @prokopowicz <https://github.com/prokopowicz>
    > Since this is a bug, I'd like to record this to JIRA issue before merging.
    > Could you file a JIRA, please?
    >
    > —
    > Reply to this email directly or view it on GitHub
    > <https://github.com/apache/storm/pull/758#issuecomment-145993674>.
    >



> 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.11.0
>            Reporter: Pete Prokopowicz
>              Labels: patch
>
> 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)