[IMPALA-7321] Write permissions checks for insert into multi-level partitioned table are incorrect

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Frontend
• Epic Color: ghx-label-4
• Assignee: Unassigned
• Reporter: Todd Lipcon
• Created: 19/Jul/18 02:00
• Updated: 29/Sep/23 10:00

Description

Currently, the logic to determine whether a table has write access is a bit incorrect: we check each existing partition, and we check the top-level location for the table. However, if a table uses partitioning on multiple levels, we could have the following situation:

table/ (read-write)
table/x=1/ (read-only)
table/x=1/y=1/ (read-write)

In this case, the table would pass the check and be determined to be "writable" but in fact an attempt to create a new partition such as x=1/y=2 would fail in the backend.

Issue Links

• is related to: IMPALA-7539 Support HDFS permissions checks with LocalCatalog
• relates to: IMPALA-12472 Skip permission check when refreshing in event processor
• relates to: IMPALA-7320 Loading HDFS tables calls getFileStatus on each partition serially