[
https://issues.apache.org/jira/browse/TEZ-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067339#comment-14067339
]
Mohammad Kamrul Islam commented on TEZ-1057:
--------------------------------------------
Thanks Bikas.
So we need to do the same for Writer/Reader interface as well.
These empty interfaces have sub-interfaces KeyValue(s)Reader and KeyValueWriter.
Do you want these to be abstract class as well?
In related note, I hit a Java issue to convert implements to extends.
{noformat}
public class MapProcessor extends MRTask implements LogicalIOProcessor {
{noformat}
{noformat}
public class ReduceProcessor extends MRTask implements LogicalIOProcessor {
{noformat}
Any cleaner solution for these two cases of multiple inheritance?
> Replace interfaces with abstract classes for Processor/Input/Output classes
> ---------------------------------------------------------------------------
>
> Key: TEZ-1057
> URL: https://issues.apache.org/jira/browse/TEZ-1057
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Mohammad Kamrul Islam
> Priority: Blocker
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
