Istvan Toth created PHOENIX-6652:
------------------------------------
Summary: phoenix.schema.mapSystemTablesToNamespace behaviour
inconsistenct with docs
Key: PHOENIX-6652
URL: https://issues.apache.org/jira/browse/PHOENIX-6652
Project: Phoenix
Issue Type: Bug
Components: core
Reporter: Istvan Toth
According to the docs, phoenix.schema.mapSystemTablesToNamespace needs to be
set both on the client and server side.
However, it only seems to have an effect on the client side, which is even
codified in the MigrateSystemTablesToSystemNamespaceIT tests, which change
this in the client side only, and expect Phoenix to work.
We do check if phoenix.schema.isNamespaceMappingEnabled is identical on the
client and server side, but make no effort to check this for
mapSystemTablesToNamespace.
It is also not clear to me what is the use case for setting
mapSystemTablesToNamespace to off ? Backwards compatibility with ancient
clients ?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
