[jira] [Created] (IMPALA-9602) Local catalog cache treats table names as case-sensitive

[Aman Sinha (Jira)]

Aman Sinha created IMPALA-9602:
----------------------------------

             Summary: Local catalog cache treats table names as case-sensitive
                 Key: IMPALA-9602
                 URL: https://issues.apache.org/jira/browse/IMPALA-9602
             Project: IMPALA
          Issue Type: Bug
          Components: Catalog, Frontend
    Affects Versions: Impala 3.4.0
            Reporter: Aman Sinha


Start up Impala with local catalog enabled.
{noformat}
start-impala-cluster.py --catalogd_args="--catalog_topic_mode=minimal" 
--impalad_args="--use_local_catalog=true"
{noformat}

Then create a database 'db1' and a table and run the sequence of DROP, CREATE 
table with an upper-case database name (using upper-case is important for the 
repro)..this throws an AnalysisException:
{noformat}
  create database db1;
  use db1;
  create table ddl_test1 (val string);

Run the DROP / CREATE using upper-case database name DB1:
$ impala-shell -q "drop table if exists DB1.ddl_test1 purge; create table 
DB1.ddl_test1 (val string);"

Server version: impalad version 3.4.0-SNAPSHOT DEBUG (build 
76061331781e67b90d7750abadfaf8b013dc64a5)
Query: drop table if exists DB1.ddl_test1 purge
+-------------------------+
| summary                 |
+-------------------------+
| Table has been dropped. |
+-------------------------+
Fetched 1 row(s) in 0.68s
Query: create table DB1.ddl_test1 (val string)
ERROR: AnalysisException: Table already exists: DB1.ddl_test1

Could not execute command: create table DB1.ddl_test1 (val string)
{noformat}

NOTE: The above sequence may have to be run a few times. Also using either 
lower-case name 'db1' instead of 'DB1' or running with the remote catalog does 
not reproduce the problem.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)