You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by HeartSaVioR <gi...@git.apache.org> on 2017/02/27 12:19:46 UTC

[GitHub] storm issue #1970: STORM-2383 Support HBase as state backend (1.x)

Github user HeartSaVioR commented on the issue:

    https://github.com/apache/storm/pull/1970
  
    I chose this approach (all KVs to one cf in one row) because this is only guaranteed way for HBase to insert/delete atomically.
    
    If we're OK to apply the changeset (in commit phase) without atomicity, we can make state scalable via having each row. Changeset still need to be put with atomic manner so that we don't have partial changeset as `prepared changeset`. Normally changeset don't grow too much so it doesn't hurt much for scalability.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---