[
https://issues.apache.org/jira/browse/BOOKKEEPER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418853#comment-13418853
]
Sijie Guo commented on BOOKKEEPER-310:
--------------------------------------
@Flavio, yes ur right. BOOKKEEPER-309, BOOKKEEPER-310, BOOKKEEPER-311 should
work together for BOOKKEEPER-331. A better way is to put them together into one
patch in BOOKKEEPER-331, but Mridul preferred to put them as separated patches.
so BOOKKEEPER-309, BOOKKEEPER-310, BOOKKEEPER-311 would be committed until all
of them passed reviews.
> Changes in hedwig server to support JMS spec
> --------------------------------------------
>
> Key: BOOKKEEPER-310
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-310
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Mridul Muralidharan
> Attachments: BOOKKEEPER-310.diff, hedwig-server.patch,
> hedwig-server.patch.1, hedwig-server.patch.3, hedwig-server.patch.4
>
>
> The primary changes are :
> a) Support modified protocol changes (optional body).
> b) Return the published message's seq-id in the response.
> c) Minor bugfix to Array indexing in bucket which was triggered in a testcase.
--
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
