[
https://issues.apache.org/jira/browse/APEXCORE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795105#comment-15795105
]
ASF GitHub Bot commented on APEXCORE-580:
-----------------------------------------
GitHub user bhupeshchawda opened a pull request:
https://github.com/apache/apex-core/pull/440
[REVIEW ONLY] - APEXCORE-580-581 custom control tuple support
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bhupeshchawda/apex-core
APEXCORE-580-581-custom-control-tuples
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/440.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 #440
----
commit 372acaa255763db8f1e3ca349704ce57f6678ce1
Author: bhupeshchawda <[email protected]>
Date: 2016-12-28T10:18:42Z
Initial version working
commit 85113df6366d27a4d542e8b7b86a1fb3833cd064
Author: bhupeshchawda <[email protected]>
Date: 2017-01-02T05:21:41Z
putControl bug fix
commit c8c969600073b2fff36330a20276ae85539ee91b
Author: bhupeshchawda <[email protected]>
Date: 2017-01-02T12:33:20Z
Added propogate option to ControlAwareDefaultOutputPort. Fixed Thread Local.
commit c61c9f269ab88be47f96179ecc49af56041a1899
Author: bhupeshchawda <[email protected]>
Date: 2017-01-03T08:43:20Z
Bug fix- CCT was not unwrapped. Also added documentation
commit e9af367cccb6bc34c08e45ae375711422d79a2df
Author: bhupeshchawda <[email protected]>
Date: 2017-01-03T11:35:31Z
Added license headers
commit a45905c6eacafc02d4473ede802827fdac26fc51
Author: bhupeshchawda <[email protected]>
Date: 2017-01-03T12:57:41Z
Refactorings
----
> Interface for processing and emitting control tuples
> ----------------------------------------------------
>
> Key: APEXCORE-580
> URL: https://issues.apache.org/jira/browse/APEXCORE-580
> Project: Apache Apex Core
> Issue Type: Sub-task
> Reporter: David Yan
>
> DefaultOutputPort needs to have a emitControl method so that operator code
> can call to emit a control tuple.
> DefaultInputPort needs to have a processControl method so that operator would
> be able to act on the arrival of a control tuple.
> Similar to a regular data tuple, we also need to provide a way for the user
> to provide custom serialization for the control tuple.
> We need to design this so that the default behavior is to propagate control
> tuples to all output ports, and it should allow the user to easily change
> that behavior. The user can selectively propagate control tuples to certain
> output ports, or block the propagation altogether.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
