Sai Hemanth Gantasala created IMPALA-14524:
----------------------------------------------
Summary: Modify
test_concurrent_rename.py::TestConcurrentRename::test_rename_invalidate to run
asynchronously
Key: IMPALA-14524
URL: https://issues.apache.org/jira/browse/IMPALA-14524
Project: IMPALA
Issue Type: Bug
Reporter: Sai Hemanth Gantasala
Assignee: Sai Hemanth Gantasala
When enable_reload_events is true, the following test fails
{code:java}
test_concurrent_rename.py::TestConcurrentRename::test_rename_invalidate
test_event_processing.py::TestSelfRenameEvent::test_self_rename_events{code}
with the following error:
{code:java}
E20251103 12:05:30.191666 67813 JniUtil.java:184]
b949ad30810f092b:e552e9e100000000] Error in INVALIDATE TABLE
test_rename_invalidate_2ec65a1e.tbl issued by saihemanth. Time spent: 4s943ms
I20251103 12:05:30.191995 67813 jni-util.cc:321]
b949ad30810f092b:e552e9e100000000] java.lang.NullPointerException: tbl is null
in INVALIDATE TABLE test_rename_invalidate_2ec65a1e.tbl issued by saihemanth
at
com.google.common.base.Preconditions.checkNotNull(Preconditions.java:921)
at
org.apache.impala.service.CatalogOpExecutor.execResetMetadataImpl(CatalogOpExecutor.java:7428)
at
org.apache.impala.service.CatalogOpExecutor.execResetMetadata(CatalogOpExecutor.java:7288)
at
org.apache.impala.service.JniCatalog.lambda$resetMetadata$4(JniCatalog.java:331)
at
org.apache.impala.service.JniCatalogOp.lambda$execAndSerialize$1(JniCatalogOp.java:90)
at org.apache.impala.service.JniCatalogOp.execOp(JniCatalogOp.java:58)
at
org.apache.impala.service.JniCatalogOp.execAndSerialize(JniCatalogOp.java:89)
at
org.apache.impala.service.JniCatalogOp.execAndSerialize(JniCatalogOp.java:100)
at
org.apache.impala.service.JniCatalog.execAndSerialize(JniCatalog.java:243)
at
org.apache.impala.service.JniCatalog.execAndSerialize(JniCatalog.java:257)
at
org.apache.impala.service.JniCatalog.resetMetadata(JniCatalog.java:330) {code}
The reason is that both the tests run with catalog config option
'catalogd_table_rename_delay' which sleeps for 5secs before firing alter-table
event to HMS. This config blocks the invalidate query to wait to fire the
Reload event. The expectation is thet reload event is fired before alter_table
event.
The fix is to modify the tests to run the invalidate metadata queries in
asynchronous mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
