[
https://issues.apache.org/jira/browse/TAJO-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147739#comment-14147739
]
Jaehwa Jung commented on TAJO-1067:
-----------------------------------
I found this issue that is depended upon by ALTER TABLE ADD/DROP PARTITION
statement. I implemented the patch for this issue by checking existing
partition directories. As a result, I could insert overwrite the result data
without removing existing another partition directories. But the patch couldn't
merge existing row numbers. I expect that I can resolve by ALTER TABLE ADD/DROP
PARTITION statement.
> INSERT OVERWRITE INTO should not remove all partitions.
> -------------------------------------------------------
>
> Key: TAJO-1067
> URL: https://issues.apache.org/jira/browse/TAJO-1067
> Project: Tajo
> Issue Type: Bug
> Components: query master
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Priority: Critical
> Fix For: 0.9.0
>
>
> Currently, INSERT OVERWRITE INTO always moves the result data into the
> original table location. As a result, all existing partitions have been
> removed. The query should not remove all partitions because existing
> partitions may be a dataset for a production cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
