[
https://issues.apache.org/jira/browse/TAJO-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155875#comment-14155875
]
ASF GitHub Bot commented on TAJO-1067:
--------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/161#discussion_r18317268
--- Diff:
tajo-core/src/test/java/org/apache/tajo/engine/query/TestTablePartitions.java
---
@@ -485,6 +483,45 @@ public final void
testInsertIntoColumnPartitionedTableByThreeColumns() throws Ex
"R,3,3,49.0\n" +
"R,3,3,49.0\n";
assertEquals(expected, resultSetData);
+
+ // insert overwrite into already exists partitioned table with
COLUMN_PARITION_REMOVE_ALL_PARTITIONS is false
--- End diff --
COLUMN_PARITION_REMOVE_ALL_PARTITIONS was already removed. So, you need to
revise this comment line.
> 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)
