[
https://issues.apache.org/jira/browse/TAJO-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyunsik Choi updated TAJO-337:
------------------------------
Description:
Currently, Tajo uses HDFS as a primary storage. But, as a data warehouse
system, Tajo should easily support various data sources.
For this, I propose a generic storage handler interface that provides common
storage methods as follows:
* splitting input data
* locality
* accessing catalog (if providing)
* creating a table
* removing a table
* adding default table properties and validating properties
* committing, rollback, and clean up output tables
* getting table physical information like table volumes and others
* managing connection pool for connection-based storages
* adding storage-specified rewrite rules
* adding hooks for query phases
* storage properties like instant random access, indexible, read throughput,
and write throughput
was:
Currently, Tajo uses HDFS as a primary storage. But, as a data warehouse
system, Tajo should easily support various data sources.
For this, I propose a generic storage handler interface that provides common
storage methods as follows:
* splitting input data
* locality
* accessing catalog (if providing)
* creating a table
* removing a table
* adding default table properties and validating properties
* committing, rollback, and clean up output tables
* getting table physical information like table volumes and others
* managing connection pool for connection-based storages
* adding storage-specified rewrite rules
* adding hooks for query phases
> Generic StorageManager to provide common storage methods
> --------------------------------------------------------
>
> Key: TAJO-337
> URL: https://issues.apache.org/jira/browse/TAJO-337
> Project: Tajo
> Issue Type: Improvement
> Components: catalog, storage
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
>
> Currently, Tajo uses HDFS as a primary storage. But, as a data warehouse
> system, Tajo should easily support various data sources.
> For this, I propose a generic storage handler interface that provides common
> storage methods as follows:
> * splitting input data
> * locality
> * accessing catalog (if providing)
> * creating a table
> * removing a table
> * adding default table properties and validating properties
> * committing, rollback, and clean up output tables
> * getting table physical information like table volumes and others
> * managing connection pool for connection-based storages
> * adding storage-specified rewrite rules
> * adding hooks for query phases
> * storage properties like instant random access, indexible, read throughput,
> and write throughput
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
