Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)

STEPS TO REPRODUCE:

1. Create a Phoenix connection

2. CREATE SCHEMA test

3. DROP SCHEMA test

4. Now create the test schema again. This will throw below exceptions :

0: jdbc:phoenix:> create schema "test"; 
Error: ERROR 721 (42M04): Schema with given name already exists schemaName=test (state=42M04,code=721) org.apache.phoenix.schema.SchemaAlreadyExistsException: ERROR 721 (42M04): Schema with given name already exists schemaName=test

5. Now attempt to drop the test schema again:

0: jdbc:phoenix:> drop schema "test";Error: ERROR 722(43M05):Schema does not exists schemaName=test (state=43M05,code=722) org.apache.phoenix.schema.SchemaNotFoundException: ERROR 722(43M05):Schema does not exists schemaName=test

If you look in Hbase and list_namespace, you will see the test schema still exists.

ROOT CAUSE : This is a known issue discussed in Apache JIRA PHOENIX-3694

SOLUTION : Issue is fixed in Phoenix 4.10. For a backport hotfix , please log a case with HWX.

851 Views
0 Kudos
Comments
New Contributor

If you see the error, it is clearly mentioned that 'test' schema is already exist, thats why u got that error.

But while dropping the schema , it must be empty.

Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
1 of 1
Last update:
‎06-04-2017 08:59 AM
Updated by:
 
Contributors
Top Kudoed Authors