apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-580) Interface for processing and emitting control tuples
Date Mon, 06 Mar 2017 12:48:33 GMT

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

ASF GitHub Bot commented on APEXCORE-580:
-----------------------------------------

GitHub user bhupeshchawda opened a pull request:

    https://github.com/apache/apex-core/pull/482

    APEXCORE-580 APEXCORE-581 Renamed UserDefinedControlTuple to ControlT…

    …uple
    @PramodSSImmaneni Please see.
    Also regarding your second comment regarding control aware stream:
    
    The control tuple awareness here is for them to be able to wrap the user's control tuple
in a new CustomControlTuple which is only accessible to the engine. The de-multiplexing still
happens at the nodes.
    
    Do let me know if you are fine with this.

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-changes

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

    https://github.com/apache/apex-core/pull/482.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 #482
    
----
commit b6ee06c61f7b03a55b322de89c83b213f710abaf
Author: bhupeshchawda <bhupesh@apache.org>
Date:   2017-03-06T12:44:21Z

    APEXCORE-580 APEXCORE-581 Renamed UserDefinedControlTuple to ControlTuple

----


> 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
>            Assignee: Bhupesh Chawda
>             Fix For: 3.6.0
>
>
> 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.15#6346)

Mime
View raw message