[
https://issues.apache.org/jira/browse/BOOKKEEPER-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673229#comment-13673229
]
Ivan Kelly commented on BOOKKEEPER-616:
---------------------------------------
Ok. This seems ok. It changes the guarantees that we give though, as A & B will
not necessarily see all messages in order. For example, if I subscribe to T
with S1 not knowing that someone else has also subscribed to T with S1, I will
expect to see all messages, and this may not be the case. For this reason, we
should make consumer cluster a more explicit construct. This isn't hard to do.
We can simply add an option to subscription options to say this is a cluster
subscription. If a non cluster subscription then tries to subscribe, it will be
given an error.
> Add Queue Semantic for Hedwig
> -----------------------------
>
> Key: BOOKKEEPER-616
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-616
> Project: Bookkeeper
> Issue Type: New Feature
> Components: hedwig-client, hedwig-server
> Reporter: Jiannan Wang
> Attachments: Design for Message Queue Model .pdf
>
>
> Add message queue semantic to enlarge Hedwig's feature sets.
--
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
