[
https://issues.apache.org/jira/browse/TAJO-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172199#comment-14172199
]
Hudson commented on TAJO-1067:
------------------------------
SUCCESS: Integrated in Tajo-block_iteration-branch-build #15 (See
[https://builds.apache.org/job/Tajo-block_iteration-branch-build/15/])
TAJO-1067: INSERT OVERWRITE INTO should not remove all partitions. (jaehwa)
(blrunner: rev ca5fb301bff4b38d80a523d5bece9eaf74f64ec3)
* CHANGES
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestTablePartitions.java
* tajo-core/src/main/java/org/apache/tajo/master/querymaster/Query.java
* tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java
> 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)
