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

Exception hierarchy #1

Open
dan-hook opened this issue Oct 30, 2014 · 0 comments
Open

Exception hierarchy #1

dan-hook opened this issue Oct 30, 2014 · 0 comments

Comments

@dan-hook
Copy link

Exceptions are currently handled horribly. Mostly they are logged as a warning and processing continues as if they never happened. I'm currently working on a temporary solution, but we need to consider an exception hierarchy to go with the class hierarchy. For starters:

  • Create a DatabaseConnectionException that will be thrown when an Accumulo operator class catches an exception from AccumuloException.
  • Create a TableException error that will be thrown by D4MInserterIF
  • Map MutationsRejectedException and TableNotFoundException in AccumuloInserter to the TableException
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant