[
https://issues.apache.org/jira/browse/TEZ-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544106#comment-14544106
]
Bikas Saha commented on TEZ-2450:
---------------------------------
[~rajesh.balamohan] I haven't studied the approach in the patch yet. My
question before that would be whether it would make sense to refactor these
Inputs/Outputs into their logical and physical parts? The logical part would be
partitioning output and merging inputs. The physical part would be current http
impl, or your new async impl, or something else (like proposed in TEZ-2442).
These inputs/outputs would then be specified in the DAGs, but based on
configuration they could end up using different physical transfer methods.
> support async http clients in ordered & unordered inputs
> --------------------------------------------------------
>
> Key: TEZ-2450
> URL: https://issues.apache.org/jira/browse/TEZ-2450
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Attachments: TEZ-2450.WIP.patch
>
>
> It will be helpful to switch between JDK & other async http impls. For LLAP
> scenarios, it would be useful to make http clients interruptible which is
> supported in async libraries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
