[
https://issues.apache.org/jira/browse/TAJO-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184325#comment-14184325
]
Hyunsik Choi commented on TAJO-1123:
------------------------------------
Hi guys,
You seem to make use of the volume of Fragments. The looks good to me.
Later, in my opinion, Query, SubQuery, and Repartitioner should not handle
directly concrete Fragment classes later. Also, all methods related to specific
storage should be hidden from Fragment, and each storage manager implementation
provides the storage-specified methods with its concrete Fragment.
But, these works are actually out of scope in TAJO-1123. I propose TAJO-337 for
the work.
Consequently, I think that TAJO-1123 still seems to be on this roadmap.
TAJO-1123 is just for HBase Storage Manager. If we have both HDFS and HBase
storage manager, it would be easier to derive the more detailed requirements
for Generic Storage Manager.
Could you rebase it against the latest revision? If so, I'll finish the review.
> Use Fragment instead of FileFragment.
> -------------------------------------
>
> Key: TAJO-1123
> URL: https://issues.apache.org/jira/browse/TAJO-1123
> Project: Tajo
> Issue Type: Sub-task
> Reporter: Hyoungjun Kim
> Assignee: Hyoungjun Kim
> Priority: Minor
>
> Currently most operator and planner uses FileFragment object for splitting
> data. FileFragment only has a information about a scanning target file. In
> order to support various storage this should be changed to the abstract
> object 'Fragment'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
