[IMPALA-9753] Possible bug in TRUNCATE of ACID tables on S3

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: Impala 4.0.0
• Component/s: Frontend
• Epic Color: ghx-label-8
• Assignee: Csaba Ringhofer
• Reporter: Csaba Ringhofer
• Created: 15/May/20 18:09
• Updated: 03/Jun/20 09:50
• Resolved: 03/Jun/20 09:50

Description

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.