GitHub user HeartSaVioR opened a pull request:

    https://github.com/apache/storm/pull/1970

    STORM-2383 Support HBase as state backend (1.x)

    * Implement HBase state backend
      * picked Redis state backend implementation
      * Current implementation stores prepare/commit/txids into a column family 
in a table
        * prepare, commit, txids have its row
        * they're stored to qualifier:value map (not scalable but guarantee 
atomicity)
        * we can address atomicity vs scalable later
    * Added 'how to set up' to State-checkpointing doc
    
    NOTE: Currently I can't run or debug tests on IntelliJ for master branch 
(so worked on 1.x-branch). I also heard many folks are struggling, so might be 
better to address it soon.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/HeartSaVioR/storm STORM-2383-1.x

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1970.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1970
    
----
commit 1ed4779ef42e203f1b3734a060f5aebb2d5b32cc
Author: Jungtaek Lim <[email protected]>
Date:   2017-02-27T12:01:13Z

    STORM-2383 Support HBase as state backend
    
    * Implement HBase state backend
      * picked Redis state backend implementation
      * Current implementation stores prepare/commit/txids into a column family 
in a table
        * prepare, commit, txids have its row
        * they're stored to qualifier:value map (not scalable but guarantee 
atomicity)
        * we can address atomicity vs scalable later
    * Added 'how to set up' to State-checkpointing doc

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to