[IMPALA-3455] Unable to drop AVRO table if schema file is missing

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: Impala 2.2.4
• Component/s: Frontend
• Labels: newbie
• Epic Link: avro-metadata-issues
• Assignee: Unassigned
• Reporter: Eric Lin
• Created: 29/Apr/16 06:20
• Updated: 11/Mar/24 11:53

Description

See the test case below:

host-10-17-80-18.coe.cloudera.com:21000] > CREATE external TABLE test STORED AS AVRO LOCATION '/tmp/93548/data' TBLPROPERTIES ('avro.schema.url'='/tmp/schema.json');
Query: create external TABLE test STORED AS AVRO LOCATION '/tmp/93548/data' TBLPROPERTIES ('avro.schema.url'='/tmp/schema.json')

WARNINGS: Ignoring column definitions in favor of Avro schema.
The Avro schema has 2 column(s) but 0 column definition(s) were given.
Fetched 0 row(s) in 4.08s

# after renamed the file /tmp/schema.json to /tmp/schema.json.tmp

[host-10-17-80-18.coe.cloudera.com:21000] > drop table test;
Query: drop table test
ERROR: AnalysisException: Failed to load metadata for table: case_93548.test
CAUSED BY: AnalysisException: Invalid avro.schema.url: /tmp/schema.json. Path does not exist.
CAUSED BY: TableLoadingException: Failed to load metadata for table: case_93548.test
CAUSED BY: AnalysisException: Invalid avro.schema.url: /tmp/schema.json. Path does not exist.

Same command will work OK in Hive without problems.

Issue Links

• relates to: IMPALA-5803 Database prefix does not always work properly if table with has same name