[jira] [Updated] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec
[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-309: --- Summary: Protocol changes in hedwig to support JMS spec (was: Protocol changes in hedwig to support message properties, and make body optional) > Protocol changes in hedwig to support JMS spec > -- > > Key: BOOKKEEPER-309 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309 > Project: Bookkeeper > Issue Type: Sub-task >Reporter: Mridul Muralidharan > > JMS spec compliance requires three changes to the protocol. > a) Support for message properties. > b) Make body optional (message contains only properties). > c) Return the published message's seq-id in the response. -- 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] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec
[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-309: --- Attachment: hedwig-protocol.patch Protocol changes which implement the changes mentioned in description > Protocol changes in hedwig to support JMS spec > -- > > Key: BOOKKEEPER-309 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309 > Project: Bookkeeper > Issue Type: Sub-task >Reporter: Mridul Muralidharan > Attachments: hedwig-protocol.patch > > > JMS spec compliance requires three changes to the protocol. > a) Support for message properties. > b) Make body optional (message contains only properties). > c) Return the published message's seq-id in the response. -- 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] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec
[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-309: --- Attachment: hedwig-protocol.patch.1 Protocol changes for adding metadata. It is standalone (except for hedwig-jms-client depending on it). The diffs also overlap with client publish changes - it is not possible to separate them out imo due to the generated code. > Protocol changes in hedwig to support JMS spec > -- > > Key: BOOKKEEPER-309 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309 > Project: Bookkeeper > Issue Type: Sub-task >Reporter: Mridul Muralidharan > Attachments: hedwig-protocol.patch, hedwig-protocol.patch.1 > > > JMS spec compliance requires three changes to the protocol. > a) Support for message properties. > b) Make body optional (message contains only properties). > c) Return the published message's seq-id in the response. -- 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] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec
[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-309: --- Attachment: hedwig-protocol.patch.3 Changes to protocol to return seq-id as part of publish response as per review comments. Also includes protocol change from BOOKKEEPER-78 for defining message headers. > Protocol changes in hedwig to support JMS spec > -- > > Key: BOOKKEEPER-309 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309 > Project: Bookkeeper > Issue Type: Sub-task >Reporter: Mridul Muralidharan > Attachments: hedwig-protocol.patch, hedwig-protocol.patch.1, > hedwig-protocol.patch.3 > > > JMS spec compliance requires three changes to the protocol. > a) Support for message properties. > b) Make body optional (message contains only properties). > c) Return the published message's seq-id in the response. -- 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] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec
[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-309: --- Attachment: hedwig-protocol.patch.4 Incorporate review comments - specifically : a) Move to latest apache bookkeeper trunk rev b) remove change(s) from BOOKKEEPER-78 - the rest of the patch DEPENDS on this jira patch as of now to compile and run. > Protocol changes in hedwig to support JMS spec > -- > > Key: BOOKKEEPER-309 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309 > Project: Bookkeeper > Issue Type: Sub-task >Reporter: Mridul Muralidharan > Attachments: hedwig-protocol.patch, hedwig-protocol.patch.1, > hedwig-protocol.patch.3, hedwig-protocol.patch.4 > > > JMS spec compliance requires three changes to the protocol. > a) Support for message properties. > b) Make body optional (message contains only properties). > c) Return the published message's seq-id in the response. -- 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] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec
[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-309: --- Attachment: hedwig-protocol.patch.5 Regenerated with 2.4.1 protobuffer > Protocol changes in hedwig to support JMS spec > -- > > Key: BOOKKEEPER-309 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309 > Project: Bookkeeper > Issue Type: Sub-task >Reporter: Mridul Muralidharan > Attachments: hedwig-protocol.patch, hedwig-protocol.patch.1, > hedwig-protocol.patch.3, hedwig-protocol.patch.4, hedwig-protocol.patch.5 > > > JMS spec compliance requires three changes to the protocol. > a) Support for message properties. > b) Make body optional (message contains only properties). > c) Return the published message's seq-id in the response. -- 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] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec
[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-309: -- Fix Version/s: (was: 4.2.0) > Protocol changes in hedwig to support JMS spec > -- > > Key: BOOKKEEPER-309 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309 > Project: Bookkeeper > Issue Type: Sub-task >Reporter: Mridul Muralidharan >Assignee: Mridul Muralidharan > Attachments: hedwig-protocol.patch, hedwig-protocol.patch.1, > hedwig-protocol.patch.3, hedwig-protocol.patch.4, hedwig-protocol.patch.5 > > > JMS spec compliance requires three changes to the protocol. > a) Support for message properties. > b) Make body optional (message contains only properties). > c) Return the published message's seq-id in the response. -- 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
