stackabletech / stackabletech/hbase-operator
Add properties to phoenix hbase-site.xml
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 6
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 9
Description
For a better and cleaner data handling I would like to see the following properties added to the /stackable/phoenix/bin/hbase-site.xml as well as the discovery configmap of hbase.
The phoenix hbase-site.xml can not be modified with configOverrides. This is a prerequisite for the hbase-phoenix-trino demo. During my tests phoenix did not work well with the default namespace. These properties helped stabilizing it.
<property>
<name>phoenix.schema.isNamespaceMappingEnabled</name>
<value>true</value>
</property>
<property>
<name>phoenix.schema.mapSystemTablesToNamespace</name>
<value>true</value>
</property>
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating /stackable/phoenix/bin/hbase-site.xml and the HBase discovery ConfigMap definition. Add the two requested Phoenix namespace properties to both locations, then verify that the generated configuration supports the hbase-phoenix-trino demo and does not rely on the default namespace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100