-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HBASE-28239 Auto create configured namespaces #5841
base: master
Are you sure you want to change the base?
HBASE-28239 Auto create configured namespaces #5841
Conversation
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
String[] customNamespaces = | ||
env.getMasterConfiguration().getStrings(ADDITIONAL_NAMESPACES); | ||
if (null != customNamespaces && customNamespaces.length > 0) { | ||
Arrays.stream(customNamespaces).forEach(ns -> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just follow the regular way to create these namespaces?
We have to insert system namespace here because meta table is in this namespace, so there is a cyclic dependency...
For other namespaces, I suggest to create them with your own operational scripts or some management systems, from outside the cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This improvement provides a config option for operators to create the additional namespaces during the HBase startup. This would eliminate the need to wrap createTable calls in checkAndCreateNamespace or provide separate cluster bootstrap functionality to guarantee that the namespace is created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But the code can only take effect when initializing the cluster, i.e, on the first startup of this HBase cluster... If later you changed the configuration and restart the hbase cluster, it will not take effect.
I think this will confuse our users...
No description provided.