We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
24.7.0
2.4.18, 2.6.0
The configuration of the hbaseRootdir at the role level is ignored:
--- apiVersion: hbase.stackable.tech/v1alpha1 kind: HbaseCluster spec: masters: config: hbaseRootdir: /test
The hbase-operator generates the following ConfigMap:
--- apiVersion: v1 kind: ConfigMap data: hbase-site.xml: |- <?xml version="1.0"?> <configuration> <property> <name>hbase.rootdir</name> <value>/hbase</value> </property> </configuration>
The configuration at the role-group level works as expected:
--- apiVersion: hbase.stackable.tech/v1alpha1 kind: HbaseCluster spec: masters: roleGroups: default: config: hbaseRootdir: /test
--- apiVersion: v1 kind: ConfigMap data: hbase-site.xml: |- <?xml version="1.0"?> <configuration> <property> <name>hbase.rootdir</name> <value>/test</value> </property> </configuration>
Other configuration properties could be affected as well.
No response
None
The text was updated successfully, but these errors were encountered:
Issues is still present, was not fixed by stackabletech/operator-rs#841 Bug is related to product-config and is here:
hbase-operator/rust/crd/src/lib.rs
Lines 476 to 484 in dc480ca
Sorry, something went wrong.
No branches or pull requests
Affected Stackable version
24.7.0
Affected Apache HBase version
2.4.18, 2.6.0
Current and expected behavior
The configuration of the hbaseRootdir at the role level is ignored:
The hbase-operator generates the following ConfigMap:
The configuration at the role-group level works as expected:
The hbase-operator generates the following ConfigMap:
Other configuration properties could be affected as well.
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: