Stop wrapping TableNotFoundException in TableOperations
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
**Is your feature request related to a problem? Please describe.**
Many `TableOperations` methods wrap `TableNotFoundException` in `AccumuloException`. It seems less confusing and safer to throw `TableNotFoundException` directly. This would force the calling code to properly handle the case where a table does not exist. Right now, its very easy to not know that this wrapping is happening and not properly account for it. Right now, there is a note in the javadoc for each method that wraps `TableNotFoundException` but, doing this is a lot less evident than throwing the exception directly (and also leads to problems updating and maintaining that note in the javadoc e.g., #5595)
Contributor guide
Assessment
This issue has not been assessed yet.