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

Roger Bush commented on BOOKKEEPER-181:
---------------------------------------

I added scan and appropriate test code and Mock implementation.

I also made the changes ivank recommended concerning cleaning things up a bit 
(renamed Versioned => VersionedValue, made some things inner interfaces/enums).

What still remains:

        1. Add license header (I'll do today).
        2. String versus byte [] - wondering how ugly this will make the code, 
so I was holding off.
        3. Convert to async versions, and have a sync adapter so MainTest can 
be written in synchronous fashion.  Adapter can just be a test utility.
        4. Metadata Qualifying Tests – should be possible to write a simple 
metadata acceptance test for functional correctness.  Would handle corner cases 
and check invariants using the abstract interfaces.  Could be done later.

Seems like 1-3 have to be done before it's ready to use.

I'm guessing integration into the existing codebase is simply a matter of 
putting com.yahoo.bookkeeper.metadata.plugin into it's own top-level-directory 
(?)

https://github.com/rogerbush8/BookKeeperMetadataPlugin
                
> 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
>             Fix For: 4.2.0
>
>         Attachments: hedwigscale.pdf, 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


Reply via email to