[
https://issues.apache.org/jira/browse/APEXCORE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682380#comment-15682380
]
ASF GitHub Bot commented on APEXCORE-456:
-----------------------------------------
GitHub user vrozov opened a pull request:
https://github.com/apache/apex-core/pull/420
APEXCORE-456 - Explicitly limit Server.Subscriber to one way communication
@PramodSSImmaneni Please review only.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/apex-core APEXCORE-456
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/420.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 #420
----
commit 308f1a7b0e91902ae5e6edbb614e7ea5ce975417
Author: Vlad Rozov <[email protected]>
Date: 2016-11-19T03:44:40Z
APEXCORE-456 - Explicitly limit Server.Subscriber to one way communication
----
> Explicitly limit Server.Subscriber to one way communication
> -----------------------------------------------------------
>
> Key: APEXCORE-456
> URL: https://issues.apache.org/jira/browse/APEXCORE-456
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Vlad Rozov
> Assignee: Vlad Rozov
> Fix For: 3.5.0
>
>
> In the DAG data always flows from upstream to downstream operators and buffer
> server Server.Subscriber class may explicitly shutdown input stream, does not
> need to allocate read buffer and listen to OP_READ events.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
