[
https://issues.apache.org/jira/browse/BOOKKEEPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240264#comment-13240264
]
Sijie Guo commented on BOOKKEEPER-181:
--------------------------------------
> I was thinking that in the case of hbase, we have versions for the rows
> already, so we could use those to perform the comparison: if the version
> passed as input is not current, then we don't swap.
hmm, hbase did provide versions for rows. but I not sure that HBase provide
such functionality to check current version and swap. I think it just provide
set a value associate with a version, not a CAS by version.
> Yes, it exists with zookeeper, but the current design document does not
> reflect it. You may consider updating it.
will update the document.
> It was not entirely clear to me that you're assuming zookeeper in the
> document for this part. If that's the assumption, then it seems fine to me.
will modify the document to make this part more clearly.
> Scale hedwig
> ------------
>
> Key: BOOKKEEPER-181
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-181
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server, hedwig-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Attachments: hedwigscale.pdf
>
>
> Current implementation of Hedwig and BookKeeper is designed to scale to
> hundreds of thousands of topics, but now we are looking at scaling them to
> tens to hundreds of millions of topics, using a scalable key/value store such
> as HBase.
--
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
