Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-9753

Possible bug in TRUNCATE of ACID tables on S3

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • Impala 4.0.0
    • Frontend
    • None
    • ghx-label-8

    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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            csringhofer Csaba Ringhofer
            csringhofer Csaba Ringhofer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment