[
https://issues.apache.org/jira/browse/TEZ-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated TEZ-2636:
--------------------------------
Attachment: TEZ-2636.2.txt
I don't want to change the way inputIsReady() is reported via this jira. Given
the way the system works in terms of splits and launching tasks when they're
available - event for MRInput will come in almost as soon as the task starts.
That'l likely why this hasn't been an issue. Will create a new jira to send
inputIsReady at the correct time.
I've added a fix in MultiMRInput to indicate inputIsReady for the 0 physical
input case, which would otherwise have been a problem.
> MRInput and MultiMRInput should work for cases when there are 0 physical
> inputs
> -------------------------------------------------------------------------------
>
> Key: TEZ-2636
> URL: https://issues.apache.org/jira/browse/TEZ-2636
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-2636.1.txt, TEZ-2636.2.txt
>
>
> It's possible that an Input is setup without any actual data. This is
> especially valid when a task is processing multiple MRInputs. One side has
> data, but the other does not. In such cases - we currently end up generating
> an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
