Add properties to phoenix hbase-site.xml

Open
#288 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
kubernetes

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.

Description

area/demo

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>
Dominant language
Rust
Stars
21
Forks
6
Avg merge
1d 19h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/hbase-operator

All issues in stackabletech/hbase-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.