You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by bhupeshchawda <gi...@git.apache.org> on 2017/03/06 12:48:29 UTC

[GitHub] apex-core pull request #482: APEXCORE-580 APEXCORE-581 Renamed UserDefinedCo...

GitHub user bhupeshchawda opened a pull request:

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

    APEXCORE-580 APEXCORE-581 Renamed UserDefinedControlTuple to ControlT\u2026

    \u2026uple
    @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 <bh...@apache.org>
Date:   2017-03-06T12:44:21Z

    APEXCORE-580 APEXCORE-581 Renamed UserDefinedControlTuple to ControlTuple

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-core pull request #482: APEXCORE-580 APEXCORE-581 Renamed UserDefinedCo...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---