You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/01/14 15:44:14 UTC

[jira] [Commented] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

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

Ivan Kelly commented on BOOKKEEPER-311:
---------------------------------------

This was committed with BOOKKEEPER-331.
                
> Changes in hedwig client api to support JMS spec
> ------------------------------------------------
>
>                 Key: BOOKKEEPER-311
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-311
>             Project: Bookkeeper
>          Issue Type: Sub-task
>            Reporter: Mridul Muralidharan
>            Assignee: Mridul Muralidharan
>         Attachments: hedwig-client-consume.patch.1, hedwig-client.patch, hedwig-client.patch.3, hedwig-client.patch.4, hedwig-client.patch.5, hedwig-client-publish.patch.1
>
>
> Primary changes are :
> a) Add support for returning seq-id for a publish request. This is an api change (backwardly compatible for users).
> b) Make consume a sync consume, with addition of an asyncConsume - this is to ensure that invoking consume() ensure request makes to server before returning (with what reasonable gaurantees that netty allows).
> c) Ensure that explicit close'ing of session will flush buffered consume seq-id's when auto-ack is enabled (default in hedwig java client).
> In addition, there are also fixes for
> d) Fix NPE's observed as part of testing JMS provider.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira