Impala 4.4.0 was released 2 months ago on 2024-05-25. There are
several bugs that block it from being used in production. I think we
should make a maintenance release of 4.4.1 to fix them. Here are the
list of issues:

Critical Fixes
IMPALA-13107: Don't start query on executor if instance number equals 0
IMPALA-13129: Move runtime filter skipping at registerRuntimeFilter
IMPALA-13130: Prioritize EndDataStream messages
IMPALA-13138: Never smallify existing StringValue objects, only new
ones during DeepCopy
IMPALA-13161: Fix column index overflow in DelimitedTextParser
IMPALA-13152: Avoid NaN, infinite, and negative ProcessingCost
IMPALA-13150: Possible buffer overflow in StringVal::CopyFrom()
IMPALA-13057: Incorporate tuple/slot information into tuple cache key

Nice-to-have
IMPALA-13203: Rewrite 'id = 0 OR false' as expected
IMPALA-13252: Consistently use PrintId to print TUniqueId
IMPALA-9441,IMPALA-13170: Ops listing dbs/tables should handle db not exists
IMPALA-13028: Strip dynamic link libraries in Linux DEB/RPM packages
IMPALA-13134: DDL hang with SYNC_DDL enabled when Catalogd is changed
to standby status
IMPALA-13143: Fix flaky test_catalogd_failover_with_sync_ddl
IMPALA-13119: Fix cost_ initialization at CostingSegment.java
IMPALA-13077: Fix selectivity estimation for SEMI JOIN
IMPALA-13076 Add pstack and jstack to Impala Redhat docker images
IMPALA-13058: Init first_arrival_time_ and completion_time_ with -1
IMPALA-13040: Add waiting mechanism in UpdateFilterFromRemote
IMPALA-13040: (addendum) Inject larger delay for sanitized build
IMPALA-13035: Querying metadata tables from non-Iceberg tables throws
IllegalArgumentException
IMPALA-13034: Add logs and counters for HTTP profile requests blocking
client fetches
IMPALA-12712: Invalidate metadata on table should set better createEventId
IMPALA-12680: Fix NullPointerException during AlterTableAddPartitions
IMPALA-13159: Fix query cancellation caused by statestore failover
IMPALA-10451: Fix avro table loading failures caused by HIVE-24157

I propose that we release 4.4.1 soon. I'm willing to volunteer as the
release manager. I'm interested to hear what the community thinks
about doing a release. All feedback is welcome!

Thanks,
Quanlong

Reply via email to