Search before asking

• I had searched in the feature and found no similar feature requirement.

Description

The current AssertSinkWriter has a bug in the Close method to verify whether the data has been run completely, especially when dealing with multiple concurrent instances.
For example, if there are two AssertSinkWriter threads A and B, and A has finished running while B has not, A will execute the close method to count whether the overall execution is complete.

The correct logic is to perform validation after all threads have completed running, or alternatively, thread A only verifies the data it runs.

• link [fix][connector-v2][connector-assert] Optimize Assert Sink verification method #8356

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct