[jira] [Updated] (PHOENIX-6214) client connect throw NEWER_SCHEMA_FOUND exception after phoenix.schema.isNamespaceMappingEnabled is true
[ https://issues.apache.org/jira/browse/PHOENIX-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6214: - Priority: Major (was: Blocker) > client connect throw NEWER_SCHEMA_FOUND exception after > phoenix.schema.isNamespaceMappingEnabled is true > > > Key: PHOENIX-6214 > URL: https://issues.apache.org/jira/browse/PHOENIX-6214 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.13.1 >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Major > > after set phoenix.schema.isNamespaceMappingEnabled is true, input “use > "SYSTEM"” by sqlline.py,and quit sqlline. there throw > NewerSchemaAlreadyExistsException when get into sqlline again. As shown below: > org.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 > (42M04): Schema with given name already exists > schemaName=SYSTEMorg.apache.phoenix.schema.NewerSchemaAlreadyExistsException: > ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEM at > org.apache.phoenix.schema.MetaDataClient.createSchema(MetaDataClient.java:4111) > at > org.apache.phoenix.compile.CreateSchemaCompiler$1.execute(CreateSchemaCompiler.java:46) > at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394) at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:377) at > org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6214) client connect throw NEWER_SCHEMA_FOUND exception after phoenix.schema.isNamespaceMappingEnabled is true
[ https://issues.apache.org/jira/browse/PHOENIX-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-6214: --- Attachment: (was: 123.png) > client connect throw NEWER_SCHEMA_FOUND exception after > phoenix.schema.isNamespaceMappingEnabled is true > > > Key: PHOENIX-6214 > URL: https://issues.apache.org/jira/browse/PHOENIX-6214 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.13.1 >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Blocker > > after set phoenix.schema.isNamespaceMappingEnabled is true, input “use > "SYSTEM"” by sqlline.py,and quit sqlline. there throw > NewerSchemaAlreadyExistsException when get into sqlline again. As shown below: > org.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 > (42M04): Schema with given name already exists > schemaName=SYSTEMorg.apache.phoenix.schema.NewerSchemaAlreadyExistsException: > ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEM at > org.apache.phoenix.schema.MetaDataClient.createSchema(MetaDataClient.java:4111) > at > org.apache.phoenix.compile.CreateSchemaCompiler$1.execute(CreateSchemaCompiler.java:46) > at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394) at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:377) at > org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6214) client connect throw NEWER_SCHEMA_FOUND exception after phoenix.schema.isNamespaceMappingEnabled is true
[ https://issues.apache.org/jira/browse/PHOENIX-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-6214: --- Attachment: 123.png > client connect throw NEWER_SCHEMA_FOUND exception after > phoenix.schema.isNamespaceMappingEnabled is true > > > Key: PHOENIX-6214 > URL: https://issues.apache.org/jira/browse/PHOENIX-6214 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.13.1 >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Blocker > Attachments: 123.png > > > after set phoenix.schema.isNamespaceMappingEnabled is true, input “use > "SYSTEM"” by sqlline.py,and quit sqlline. there throw > NewerSchemaAlreadyExistsException when get into sqlline again. As shown below: > org.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 > (42M04): Schema with given name already exists > schemaName=SYSTEMorg.apache.phoenix.schema.NewerSchemaAlreadyExistsException: > ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEM at > org.apache.phoenix.schema.MetaDataClient.createSchema(MetaDataClient.java:4111) > at > org.apache.phoenix.compile.CreateSchemaCompiler$1.execute(CreateSchemaCompiler.java:46) > at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394) at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:377) at > org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6214) client connect throw NEWER_SCHEMA_FOUND exception after phoenix.schema.isNamespaceMappingEnabled is true
[ https://issues.apache.org/jira/browse/PHOENIX-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-6214: --- Description: after set phoenix.schema.isNamespaceMappingEnabled is true, input “use "SYSTEM"” by sqlline.py,and quit sqlline. there throw NewerSchemaAlreadyExistsException when get into sqlline again. As shown below: org.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEMorg.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEM at org.apache.phoenix.schema.MetaDataClient.createSchema(MetaDataClient.java:4111) at org.apache.phoenix.compile.CreateSchemaCompiler$1.execute(CreateSchemaCompiler.java:46) at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394) at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:377) at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) was: after set phoenix.schema.isNamespaceMappingEnabled is true, input “use "SYSTEM"” by sqlline.py,and quit sqlline. throw NewerSchemaAlreadyExistsException when get into sqlline again. As shown below: org.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEMorg.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEM at org.apache.phoenix.schema.MetaDataClient.createSchema(MetaDataClient.java:4111) at org.apache.phoenix.compile.CreateSchemaCompiler$1.execute(CreateSchemaCompiler.java:46) at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394) at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:377) at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) > client connect throw NEWER_SCHEMA_FOUND exception after > phoenix.schema.isNamespaceMappingEnabled is true > > > Key: PHOENIX-6214 > URL: https://issues.apache.org/jira/browse/PHOENIX-6214 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.13.1 >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Blocker > > after set phoenix.schema.isNamespaceMappingEnabled is true, input “use > "SYSTEM"” by sqlline.py,and quit sqlline. there throw > NewerSchemaAlreadyExistsException when get into sqlline again. As shown below: > org.apache.phoenix.schema.NewerSchemaAlreadyExistsException: ERROR 721 > (42M04): Schema with given name already exists > schemaName=SYSTEMorg.apache.phoenix.schema.NewerSchemaAlreadyExistsException: > ERROR 721 (42M04): Schema with given name already exists schemaName=SYSTEM at > org.apache.phoenix.schema.MetaDataClient.createSchema(MetaDataClient.java:4111) > at > org.apache.phoenix.compile.CreateSchemaCompiler$1.execute(CreateSchemaCompiler.java:46) > at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:394) at > org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:377) at > org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) -- This message was sent by Atlassian Jira (v8.3.4#803005)
