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

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

GitHub user wurstmeister opened a pull request:

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

    STORM-428: extracted ITuple interface

    * updated version of https://github.com/apache/storm/pull/221 on top of 
latest changes
    * replaced MockTridentTuple with TridentTupleView.createFreshTuple()
    


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

    $ git pull https://github.com/wurstmeister/incubator-storm STORM-428-fixed

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

    https://github.com/apache/storm/pull/271.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 #271
    
----
commit d2ca0b344fe685c2978c55b9792cde1ef8273eda
Author: wurstmeister <[email protected]>
Date:   2014-08-09T12:03:25Z

    STORM-428: extracted ITuple interface
    
    * removed MockTridentTuple to avoid duplication

commit 9553b1486b35b35d5895ded1cc892096aadf3055
Author: wurstmeister <[email protected]>
Date:   2014-09-25T22:13:58Z

    STORM-428: fixed TridentKafkaTest
    
    * added changelog entry

----


> Common Core Storm/Trident Tuple Interface
> -----------------------------------------
>
>                 Key: STORM-428
>                 URL: https://issues.apache.org/jira/browse/STORM-428
>             Project: Apache Storm
>          Issue Type: Improvement
>            Reporter: P. Taylor Goetz
>            Priority: Minor
>
> Currently core storm and trident tuples do not share a common interface. For 
> developers creating libraries that perform tuple processing logic that can be 
> used in both core storm and trident topologies, this means that logic must be 
> implemented twice: once for each tuple type.
> It would be nice if we could eliminate this limitation.



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

Reply via email to