[IMPALA-4342] "Cannot drop non-empty database: udf_test_errors" when using local filesystem

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Impala 2.8.0
• Fix Version/s: Impala 2.8.0
• Component/s: Infrastructure
• Labels: broken-build
• Assignee: Michael Ho
• Reporter: Jim Apple
• Created: 21/Oct/16 22:57
• Updated: 11/Nov/16 13:12
• Resolved: 11/Nov/16 13:12

Description

TestUdfs.test_udf_errors[exec_option: {'disable_codegen': False, 'abort_on_error': 1, 'exec_single_node_rows_threshold': 0, 'batch_size': 0, 'num_nodes': 0} | table_format: text/none] 
[gw1] linux2 -- Python 2.6.6 /data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/bin/../infra/python/env/bin/python
query_test/test_udfs.py:81: in test_udf_errors
    self.run_test_case('QueryTest/udf-errors', vector)
common/impala_test_suite.py:320: in run_test_case
    result = self.__execute_query(target_impalad_client, query, user=user)
common/impala_test_suite.py:511: in __execute_query
    return impalad_client.execute(query, user=user)
common/impala_connection.py:160: in execute
    return self.__beeswax_client.execute(sql_stmt, user=user)
beeswax/impala_beeswax.py:173: in execute
    handle = self.__execute_query(query_string.strip(), user=user)
beeswax/impala_beeswax.py:337: in __execute_query
    handle = self.execute_query_async(query_string, user=user)
beeswax/impala_beeswax.py:333: in execute_query_async
    return self.__do_rpc(lambda: self.imp_service.query(query,))
beeswax/impala_beeswax.py:458: in __do_rpc
    raise ImpalaBeeswaxException(self.__build_error_message(b), b)
E   ImpalaBeeswaxException: ImpalaBeeswaxException:
E    INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
E    MESSAGE: AnalysisException: Cannot drop non-empty database: udf_test_errors

I think this was from https://gerrit.cloudera.org/#/c/4651 , so I assigned to you, Michael. COuld this be some race condition? I ask because the build with the error was bf1d9677fc09dabc88ab6c71f82ec99ec59ec164
and the build right before it, which was green, was on 502220c69d483f785632eaf0030babf40be78ff4

Issue Links

• is related to: IMPALA-3641 DROP / CREATE sequence on same table failed with "table already exists"