Skip to content
New issue

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

Handle HBase exceptions for basic repository operations correctly #15

Open
asotona opened this issue Mar 22, 2017 · 0 comments
Open

Handle HBase exceptions for basic repository operations correctly #15

asotona opened this issue Mar 22, 2017 · 0 comments

Comments

@asotona
Copy link
Collaborator

asotona commented Mar 22, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant