stackabletech / stackabletech/hbase-operator
HBase ACL
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 6
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 9
Description
We want to delete data from hbase using phoenix.
Deleting data with SQL makes it very easy for the user to erease data (e.g. data needs to be deleted because a user enforces his GDPR right to be forgotten)
The pushdown is possible according to the documentation
SQL DELETE
If a WHERE clause is specified, the DELETE operation only works if the predicate in the clause can be fully pushed down to the data source.
A fully pushdown means ACL enabled on the hbase side. see https://hbase.apache.org/book.html#hbase.accesscontrol.configuration
May be a configOverride is enough (already possible for hbase), may be more is needed.
It will involve some testing efforts.
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 with the Phoenix SQL DELETE documentation and the HBase access-control configuration documentation linked in the issue. Check the operator's existing HBase configuration override entry point, then test whether ACL-enabled deployment permits fully pushed-down deletes through Phoenix; done means the configuration and behavior are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust, sql
- Domain
- databases, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100