Github user ankitsinghal commented on the pull request:

    https://github.com/apache/phoenix/pull/153#issuecomment-208944403
  
    @samarthjain , thanks for the review. 
    I'm unsure about disabling schema constructs if isNamespaceMapping is not 
enabled in config. As this property is client side property and even if it is 
unset , user can still access the table mapped to namespace created by another 
client which has this property set. This property just ensure schema mapping to 
namespace during creation of table.
    
    I think these constructs still make sense independently. but @JamesRTaylor 
/ @samarthjain , if you guys think of disabling it , I'm ok with that too.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to