nzw921rx opened a new pull request, #13299: URL: https://github.com/apache/seatunnel/pull/13299
### Purpose of this pull request Yes, I am contributing to Apache SeaTunnel. Move `IncrementalSourceStreamFetcherBridge` into `org.apache.seatunnel.benchmark.cdc`, alongside `IncrementalSourceRecordEmitterFixture`, and remove the obsolete import. Follow-up to #13212. Cache a `MethodHandle` during class initialization to call the existing package-private `shouldEmit` method. Reuse it with `invokeExact` for each record, preserving runtime exceptions and errors. The bridge itself is now package-private. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Verified on JDK 17: ```bash ./mvnw -B -Pbenchmark -pl seatunnel-benchmarks -am -DskipTests -Dskip.ui=true -Dlicense.skipAddThirdParty=true spotless:apply ./mvnw -B -q -Pbenchmark -pl seatunnel-benchmarks -am -DskipTests -Dskip.ui=true -Dlicense.skipAddThirdParty=true verify java -jar seatunnel-benchmarks/target/benchmarks.jar IncrementalSourceRecordEmitterBenchmark -f 1 -wi 0 -i 1 -r 100ms -prof gc -foe true git diff --cached --check ``` All four default 20-column cases completed successfully, including the fixture's offset-boundary, emitted-row and checkpoint-offset checks. This was a functional smoke check, not a performance comparison. Inspected the packaged JAR to confirm the bridge is next to the fixture under `benchmark/cdc`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
