[
https://issues.apache.org/jira/browse/TAJO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947618#comment-13947618
]
Hyunsik Choi commented on TAJO-30:
----------------------------------
Hi David,
Thank you for opening new tickets.
After I added the missed property to storage-default.xml, I created a parquet
format file from CTAS on a real cluster and executed some queries. it worked
well and was super fast. Your patch is unquestionable. The patch is
straightforward and contains enough unit tests. I don't have additional
comment. After your submit your in-progress work, I'll finish the review.
There may be additional issues related to Parquet, such as how to specify
column compression, how to set block or page size, and how to enable
dictionary. I think that they don't need to be solved right now. It would be
great if we create additional issues for them in order to avoid one big issue.
Thanks,
Hyunsik
> Parquet Integration
> -------------------
>
> Key: TAJO-30
> URL: https://issues.apache.org/jira/browse/TAJO-30
> Project: Tajo
> Issue Type: New Feature
> Reporter: Hyunsik Choi
> Assignee: David Chen
> Labels: Parquet
> Attachments: TAJO-30.patch, null_handling.patch
>
>
> Parquet is a columnar storage format developed by Twitter. Implement Parquet
> (http://parquet.io/) support for Tajo.
> The implementation consists of the following:
> * {{ParquetScanner}} and {{ParquetAppender}} - FileScanner and FileAppenders
> for reading and writing Parquet.
> * {{TajoParquetReader}} and {{TajoParquetWriter}} - Top-level reader and
> writer for serializing/deserializing to Tajo Tuples.
> * {{TajoReadSupport}} and {{TajoWriteSupport}} - Abstractions to perform
> conversion between Parquet and Tajo records.
> * {{TajoRecordMaterializer}} - Materializes Tajo Tuples from Parquet's
> internal representation.
> * {{TajoRecordConverter}} - Used by {{TajoRecordMateriailzer}} to
> materialize a Tajo Tuple.
> * {{TajoSchemaConverter}} - Converts between Tajo and Parquet schemas.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
