[jira] [Updated] (TEZ-857) Split Input/Output interfaces into Framework / User components

["Siddharth Seth (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TEZ-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Seth updated TEZ-857:
-------------------------------

    Attachment: TEZ-857.1.txt

Patch separates Input, Output, LogicalInput, LogicalOutput into two interfaces each.
Along these lines
Input, InputFrameworkComponent
LogicalInput, LogicalInputFrameworkComponent

AbstracLogicalInput is what writers of new Inputs are expected to extend.

[~bikassaha], [~hitesh] - review please. Suggestions for better naming are welcome.

> Split Input/Output interfaces into Framework / User components
> --------------------------------------------------------------
>
>                 Key: TEZ-857
>                 URL: https://issues.apache.org/jira/browse/TEZ-857
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: TEZ-857.1.txt
>
>
> Inputs / Outputs have several methods which are not meant for user interaction - initialize(Tez*Context), close(), TEZ-844 is adding another.
> There has been confusion in the past on whether the framework will call close, or whether it's the user's responsibility.
> The framework specific methods and the Processor usable methods can be split into a separate interface. Input/Output writers would need to implement both, Processor writers would only see the Input part of the interface.
> TEZ-782, TEZ-827 introduced some requirements on Inputs which are not enforced at compile time (must request mem). These could potentially be added to the framework part of the interface to force Inputs/Outputs to be aware of them at compile time, while not polluting the Processor interface.



--
This message was sent by Atlassian JIRA
(v6.2#6252)