[IGNITE-15598] TableManager handles exceptions in incorrect way.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-alpha2
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Andrey Mashenkov
• Created: 24/Sep/21 12:48
• Updated: 24/Sep/21 12:51

Description

IgniteTable method may throw exceptions in case of incorrect table configuration.
These exceptions must be public classes.

The first issue here is we use future.join() that wrap exceptions into CompletionException.
I think we must unwrap it to Ignite public exception (e.g. to smth like TransactionalException, ConfigurationException, or IgniteException)

The second issue, exception of internal class thrown instead and an original exception is hidden into the deep.
Now, the configuration component may throw ConfigurationValidationException, which is a public one, but it is wrapped into an internal exception ListenerRemovedException.
So, the context is lost, and such exceptions are hardly unwrapped.

PFA stacktrace.
Reproducer is available in PR for ignite-15414.

Issue Links

• is caused by: IGNITE-15414 Schema validation refactoring with configuration validators
• relates to: IGNITE-15597 Add top-level ConfigurationException class.