Handle HBase exceptions for basic repository operations correctly
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 114
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
When Halyard repository is created with type in the table name or user does not have appropriate ACLs or due to any other HBase exception - there is no easy way to fix or remove such broken repository.
Basic Halyard repository operations should return a valid response even when the related HBase table is not available to allow at least deletion of such repository from RDF4J.
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 tracing Halyard's basic repository operations and how they handle HBase exceptions, including repositories with the type in the table name and users without the required ACLs. Reproduce an unavailable-table case through RDF4J and verify that operations return valid responses, including one that permits deleting the broken repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100