Fixed Issues in Impala

Review the list of Impala issues that are resolved in Cloudera Runtime 7.3.1.

CDPD-69856: SIGSEGV crash while accessing query state from concurrent access during query execution

A crash can occur due to concurrent updates and reads of execution state, such as through the WebUI, during query processing.

Ensured atomic updates of execution state to prevent conflicts and crashes during concurrent operations.

Apache Jira: IMPALA-12747

Incorrect length when inserting multiple CHAR(N) values

When all values in a VALUES clause column are of type CHAR, but have differing lengths, Impala selects a common CHAR(max(lengths)) type, padding shorter values with spaces. This padding can lead to unexpected results if the destination column is VARCHAR or STRING, as inserting the values individually would not produce the same padded output.

The VALUES_STMT_AVOID_LOSSY_CHAR_PADDING query option was introduced to address this discrepancy. When set to true, this option prevents padding by automatically casting values to VARCHAR with the length of the longest value in the column, provided all values are CHAR and not of equal length. By default, this option is set to false.

Apache Jira: IMPALA-10753

Type mismatch in set operations with ALLOW_UNSAFE_CASTS enabled

The fix ensures that string literals are converted to numeric types correctly by considering the target type when ALLOW_UNSAFE_CASTS is enabled.

Apache Jira: IMPALA-12285