[
https://issues.apache.org/jira/browse/TAJO-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149827#comment-14149827
]
ASF GitHub Bot commented on TAJO-1067:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/161#issuecomment-57007572
I think that this feature should not depend on session variable. Session
variable works implicitly. Users can miss to check if the session variable is
enabled.
As a result, inadvertently, a user can lost his or her entire table by
```INSERT OVERWRITE``` clause.
I think that we should force users to manually use ```TRUNCATE``` statement
instead of using session variable.
> 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)
