[
https://issues.apache.org/jira/browse/TAJO-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627393#comment-14627393
]
ASF GitHub Bot commented on TAJO-1346:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/630#issuecomment-121449244
This approach seems that each individual worker directly inserts created
partitions through Catalog API. I'm concerning with too many connection
problems of catalog and explosive INSERT requests simultaneously across many
workers. It would be better if we can change it to a bulk insertion approach in
QM. How do you think of this issue?
> Run ADD PARTITION after storing column partitioned table.
> ---------------------------------------------------------
>
> Key: TAJO-1346
> URL: https://issues.apache.org/jira/browse/TAJO-1346
> Project: Tajo
> Issue Type: Sub-task
> Components: physical operator
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
>
> Currently, If new partitions are added to HDFS by ColPartitionStoreExec,
> CatalogStore will not be aware of these partitions. So, Tajo need to run
> ALTER TABLE table_name ADD PARTITION on each of the newly added partitions
> automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
