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

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

GitHub user revans2 opened a pull request:

    https://github.com/apache/incubator-storm/pull/109

    [STORM-234] Thrift purpose conf to let DRPC support authentication

    

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

    $ git pull https://github.com/revans2/incubator-storm thrift-purpose

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

    https://github.com/apache/incubator-storm/pull/109.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 #109
    
----
commit bddde9022ebb3e7e5cb1575e29d3c9fa2db23472
Author: Robert (Bobby) Evans <[email protected]>
Date:   2014-05-08T19:42:51Z

    Add thrift purpose for better configuration handling.

commit d69ad406ade961b4681eaadb8e23df71629e65b7
Author: Robert (Bobby) Evans <[email protected]>
Date:   2014-05-08T20:19:09Z

    Refactored purpose into Connection Type.

commit 9fe5e3a90cbf800c599c5bfc62b56eb547645807
Author: Robert (Bobby) Evans <[email protected]>
Date:   2014-05-09T16:11:46Z

    Updated thrift puprose and refactored it to make it cleaner.

----


> Thrift transport purpose conf
> -----------------------------
>
>                 Key: STORM-234
>                 URL: https://issues.apache.org/jira/browse/STORM-234
>             Project: Apache Storm (Incubating)
>          Issue Type: Sub-task
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>
> In a few cases it is nice to configure the thrift transport for DRPC separate 
> from the thrift transport for nimbus, but still use the same code to set them 
> up.  Todo so we have an enum that abstracts away which set of confs to use.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to