[jira] [Resolved] (IMPALA-9753) Possible bug in TRUNCATE of ACID tables on S3

["Csaba Ringhofer (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Csaba Ringhofer resolved IMPALA-9753.
-------------------------------------
    Fix Version/s: Impala 4.0
       Resolution: Fixed

> Possible bug in TRUNCATE of ACID tables on S3
> ---------------------------------------------
>
>                 Key: IMPALA-9753
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9753
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>            Reporter: Csaba Ringhofer
>            Assignee: Csaba Ringhofer
>            Priority: Critical
>             Fix For: Impala 4.0
>
>
> TRUNCATE TABLE doesn't seem to work on ACID tables in an S3 environment (with S3 guard)
> I couldn't reproduce it yet in Impala dev env, and I am not completely sure that the cause is actually S3, but found an operation that could possibly go wrong on S3:
> https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java#L2115
> Simply calling Create(Path) does create the file in HDFS, but I think that it is only created on S3 when the returned stream is closed.
> All related tests are skipped if the environment is S3, so it seems possible that the bug could slip through Impala's component tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org