tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-303) Improve FragmentProto to be extendable
Date Fri, 15 Nov 2013 05:57:21 GMT

    [ https://issues.apache.org/jira/browse/TAJO-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823322#comment-13823322

Hyunsik Choi commented on TAJO-303:

As for the relationship between Fragment and FileFragment, you are right. They need a bit
of the super-child relationship to force custom Fragment to have getTableName() method and
getProto() methods. I would be great to keep Fragment to be just a Interface rather than abstract
class. Interface would be extensible in many cases.

The asymmetric (de)serialization problem may be resolved if there are two separate methods
for a generic FragmentProto and a application-specified XXXFragmentProto.

> Improve FragmentProto to be extendable
> --------------------------------------
>                 Key: TAJO-303
>                 URL: https://issues.apache.org/jira/browse/TAJO-303
>             Project: Tajo
>          Issue Type: Improvement
>    Affects Versions: 0.8-incubating
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>         Attachments: TAJO-303.patch, TAJO-303_2.patch
> Fragment is designed to support various types of stores, and thus FragmentProto should
be designed considering the expandability.
> This issue will increase readability and productivity.

This message was sent by Atlassian JIRA

View raw message