You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (Created) (JIRA)" <ji...@apache.org> on 2012/04/06 17:25:23 UTC
[jira] [Created] (KAFKA-326)
CallbackHandler.afterDequeuingExistingData is not called during event queue
timeout
CallbackHandler.afterDequeuingExistingData is not called during event queue timeout
-----------------------------------------------------------------------------------
Key: KAFKA-326
URL: https://issues.apache.org/jira/browse/KAFKA-326
Project: Kafka
Issue Type: Bug
Components: core
Affects Versions: 0.7
Reporter: Jun Rao
Assignee: Jun Rao
CallbackHandler.afterDequeuingExistingData is only called when new events are coming and dequeued. It should be called when no new events are coming, but a queue timeout is reached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-326)
CallbackHandler.afterDequeuingExistingData is not called during event queue
timeout
Posted by "Jun Rao (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-326:
--------------------------
Resolution: Fixed
Fix Version/s: 0.7.1
Status: Resolved (was: Patch Available)
Thanks for the review.committed to trunk.
> CallbackHandler.afterDequeuingExistingData is not called during event queue timeout
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-326
> URL: https://issues.apache.org/jira/browse/KAFKA-326
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7
> Reporter: Jun Rao
> Assignee: Jun Rao
> Fix For: 0.7.1
>
> Attachments: kafka-326.patch
>
>
> CallbackHandler.afterDequeuingExistingData is only called when new events are coming and dequeued. It should be called when no new events are coming, but a queue timeout is reached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-326)
CallbackHandler.afterDequeuingExistingData is not called during event queue
timeout
Posted by "Jun Rao (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-326:
--------------------------
Status: Patch Available (was: Open)
Attached a patch.
> CallbackHandler.afterDequeuingExistingData is not called during event queue timeout
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-326
> URL: https://issues.apache.org/jira/browse/KAFKA-326
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7
> Reporter: Jun Rao
> Assignee: Jun Rao
> Attachments: kafka-326.patch
>
>
> CallbackHandler.afterDequeuingExistingData is only called when new events are coming and dequeued. It should be called when no new events are coming, but a queue timeout is reached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-326)
CallbackHandler.afterDequeuingExistingData is not called during event queue
timeout
Posted by "Neha Narkhede (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248437#comment-13248437 ]
Neha Narkhede commented on KAFKA-326:
-------------------------------------
+1. Looks good
> CallbackHandler.afterDequeuingExistingData is not called during event queue timeout
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-326
> URL: https://issues.apache.org/jira/browse/KAFKA-326
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7
> Reporter: Jun Rao
> Assignee: Jun Rao
> Attachments: kafka-326.patch
>
>
> CallbackHandler.afterDequeuingExistingData is only called when new events are coming and dequeued. It should be called when no new events are coming, but a queue timeout is reached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-326)
CallbackHandler.afterDequeuingExistingData is not called during event queue
timeout
Posted by "Jun Rao (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-326:
--------------------------
Attachment: kafka-326.patch
> CallbackHandler.afterDequeuingExistingData is not called during event queue timeout
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-326
> URL: https://issues.apache.org/jira/browse/KAFKA-326
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7
> Reporter: Jun Rao
> Assignee: Jun Rao
> Attachments: kafka-326.patch
>
>
> CallbackHandler.afterDequeuingExistingData is only called when new events are coming and dequeued. It should be called when no new events are coming, but a queue timeout is reached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira