You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Mohammad Kamrul Islam (JIRA)" <ji...@apache.org> on 2014/03/03 10:17:20 UTC

[jira] [Commented] (TEZ-695) Have Abstract class for Input/Processor/Output

    [ https://issues.apache.org/jira/browse/TEZ-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917865#comment-13917865 ] 

Mohammad Kamrul Islam commented on TEZ-695:
-------------------------------------------

[~bikassaha] , So there will be following three different cases.
1.  LogicalIOProcessor <Processor>
2. LogicalInput  <Input>
3. LogicalOutput <Output>

All are "interface" now. Should we make them to "abstract" classes. If yes, I'm concerned about LogicalIOProcessor which could be used by some existing user. -- a potential backward compatibility issue. There could will not  compile.
Input and output should be.

Would you please elaborate?

  



 

> Have Abstract class for Input/Processor/Output
> ----------------------------------------------
>
>                 Key: TEZ-695
>                 URL: https://issues.apache.org/jira/browse/TEZ-695
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>
> Currently, the context is passed to IPO objects in the initialize method and its their burden to save a copy for future use. Having an abstract class for them would allow common things like this to be done in the abstract class and reduce the burden on the IPO developer.



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