[FLINK-31014] Expose exceptions in connector testing framework

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.17.0, 1.16.1, 1.18.0
• Component/s: API / DataStream, Test Infrastructure
• Assignee: Unassigned
• Reporter: Matthias Pohl
• Created: 10/Feb/23 10:26
• Updated: 10/Feb/23 10:31

Description

I noticed for a few interfaces that we don't expose checked exceptions where it's actually useful. DataStreamSinkV2ExternalContext.createSink or ExternalSystemSplitDataWriter.writeRecords, for instance, is not exposing any Throwable except for UnsupportedOperationException. This implies that internal caught exception need to be either caught and transformed into a RuntimeException or handled internally. AFAIU, that's not what we want. The connector testing framework wants exceptions to be exposed. Therefore, we should improve the interfaces of the framework to allow exceptions to happen (probably depending on the usecase).

This makes it easier for contributors implementing test cases for their connector giving them the freedom to just expose undesired exceptions instead of handling them internally. JUnit should be the actor dealing with these exceptions.

Issue Links

• Discovered while testing: FLINK-30109 Checked exceptions are sneakingly transformed into unchecked exceptions in the Pulsar
• is caused by: FLINK-25286 Improve connector testing framework to support more scenarios