Github user JamesRTaylor commented on the pull request:
https://github.com/apache/phoenix/pull/153#issuecomment-209173008
There are likely lots of issues if isNamespaceMapping config property
changes from true to false, no? Seems like it's meant to enable/disable the
feature. Wouldn't existing namespace mapped tables not be found if it was
changed from true to false after tables had been created? What would be the
purpose of allowing a schema (namespace) to be created if the feature is off?
If none, then it's probably best to give an error message if isNamespaceMapping
is off and CREATE SCHEMA is used.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
