[
https://issues.apache.org/jira/browse/TAJO-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592988#comment-14592988
]
ASF GitHub Bot commented on TAJO-1644:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/601#issuecomment-113364944
Hi @blrunner,
Thank you for your work. How about the insert overwrite behavior for not
partitioned table? Does that the same semantic?
> When inserting empty data into a partitioned table, existing data would be
> removed.
> -----------------------------------------------------------------------------------
>
> Key: TAJO-1644
> URL: https://issues.apache.org/jira/browse/TAJO-1644
> Project: Tajo
> Issue Type: Bug
> Components: query master
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.11.0, 0.10.2
>
> Attachments: TAJO-1644.patch, TAJO-1644_2.patch
>
>
> When inserting empty data into a partitioned table, existing data would be
> removed. Tajo provides column value partition which is hive-style partition.
> In hive, when inserting empty data into a partition, there are two cases. If
> you use dynamic partitions, existing data never would be removed. But if you
> don't use dynamic partitions, existing data would be removed. When inserting
> a data to partition, tajo user don't specify each column and each column
> value. So, it is similar to dynamic partition of hive. It seems to update
> deletion logic of partitioned table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
