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

ASF GitHub Bot commented on STORM-1712:
---------------------------------------

GitHub user hustfxj opened a pull request:

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

    [STORM-1712] make storage plugin for transactional state [not to be merged 
yet]

    This is not to be merged yet. Now we support storage transactional state to 
hbase, and so on. I want to hear your opinion. If Ok, I am pleasure to create 
the PR and merge the code.

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

    $ git pull https://github.com/hustfxj/storm transactional

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

    https://github.com/apache/storm/pull/1342.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 #1342
    
----
commit e30a4e685a0446a8a5ac092d48db4581968565a4
Author: xiaojian.fxj <xiaojian....@alibaba-inc.com>
Date:   2016-04-15T16:42:02Z

    make storage plugin for transactional state

----


> make storage plugin for transactional state
> -------------------------------------------
>
>                 Key: STORM-1712
>                 URL: https://issues.apache.org/jira/browse/STORM-1712
>             Project: Apache Storm
>          Issue Type: Improvement
>            Reporter: John Fang
>            Assignee: John Fang
>
> As we know the transactional state must storage  in zk when we run trident 
> topology. In fact I have packaged the TransactionalState to a plugin. We 
> still storage the state to zk by default. But you can storage the 
> transactional state to other places by set different plugin. And we now 
> support storage transactional state to hbase, and so on. I want to hear your 
> opinion. If Ok, I am pleasure to create the PR and merge the code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to