[
https://issues.apache.org/jira/browse/STORM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148434#comment-14148434
]
ASF GitHub Bot commented on STORM-428:
--------------------------------------
Github user wurstmeister commented on the pull request:
https://github.com/apache/storm/pull/221#issuecomment-56895340
@revans2 Thanks for the feedback. I've fixed the failing test in a new PR
on top of the latest master (https://github.com/apache/storm/pull/271)
I should have made the reason for the removal of MockTridentTuple a bit
clearer. We can now use
```TridentTupleView.createFreshTuple()``` to create a new TridentTuple so
we don't need MockTridentTuple anymore.
I will close this PR in favour of (https://github.com/apache/storm/pull/271)
> 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)
