[IMPALA-8751] Kudu tables cannot be found after created

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 3.3.0
• Fix Version/s: Impala 4.0.0
• Labels: broken-build flaky
• Epic Color: ghx-label-8
• Assignee: Unassigned
• Reporter: Yongzhi Chen
• Created: 11/Jul/19 14:40
• Updated: 08/Aug/22 23:37
• Resolved: 17/Nov/20 21:04

Description

For example in some kudu integration test as:
TestKuduHMSIntegration.test_drop_db_cascade in custom_cluster/test_kudu.py
It failed with:
custom_cluster/test_kudu.py:239: in test_drop_db_cascade
assert not kudu_client.table_exists(kudu_table.name)
/usr/lib/python2.7/contextlib.py:35: in _exit_
self.gen.throw(type, value, traceback)
common/kudu_test_suite.py:165: in temp_kudu_table
kudu.delete_table(name)
kudu/client.pyx:392: in kudu.client.Client.delete_table (kudu/client.cpp:7106)
???
kudu/errors.pyx:56: in kudu.errors.check_status (kudu/errors.cpp:904)
???
E KuduNotFound: failed to drop Hive Metastore table: TException - service has thrown: NoSuchObjectException(message=s7mo1z)

And when trying to add default capabilities to kudu tables, it is sometime effective, sometimes not:
For example after enable default kudu OBJCAPABILITIES,
./run-tests.py metadata/test_ddl.py -k "create_kudu" will succeed while same test in
./run-tests.py custom_cluster/test_kudu.py :

 TestKuduHMSIntegration.test_create_managed_kudu_tables[protocol: beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0, 'disable_codegen': False, 'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format: text/none] 
custom_cluster/test_kudu.py:147: in test_create_managed_kudu_tables
    self.run_test_case('QueryTest/kudu_create', vector, use_db=unique_database)
common/impala_test_suite.py:563: in run_test_case
    result = exec_fn(query, user=test_section.get('USER', '').strip() or None)
common/impala_test_suite.py:500: in __exec_in_impala
    result = self.__execute_query(target_impalad_client, query, user=user)
common/impala_test_suite.py:798: in __execute_query
    return impalad_client.execute(query, user=user)
common/impala_connection.py:184: in execute
    return self.__beeswax_client.execute(sql_stmt, user=user)
beeswax/impala_beeswax.py:187: in execute
    handle = self.__execute_query(query_string.strip(), user=user)
beeswax/impala_beeswax.py:362: in __execute_query
    handle = self.execute_query_async(query_string, user=user)
beeswax/impala_beeswax.py:356: in execute_query_async
    handle = self.__do_rpc(lambda: self.imp_service.query(query,))
beeswax/impala_beeswax.py:519: in __do_rpc
    raise ImpalaBeeswaxException(self.__build_error_message(b), b)
E   ImpalaBeeswaxException: ImpalaBeeswaxException:
E    INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
E    MESSAGE: AnalysisException: Write not supported. Table test_create_managed_kudu_tables_a8d11828.add  access type is: READONLY

Issue Links

• is caused by: HIVE-20679 DDL operations on hive might create large messages for DBNotification
• is caused by: HIVE-21307 Need to set GzipJSONMessageEncoder as default config for EVENT_MESSAGE_FACTORY.
• is related to: KUDU-3201 Support gzipped HMS notifications (GzipJSONMessageEncoder)
• relates to: IMPALA-10058 Kudu queries hit error "Unable to deserialize scan token"