rangareddy commented on PR #19485: URL: https://github.com/apache/hudi/pull/19485#issuecomment-5262633798
Both review nits addressed in `1d01b62`, and the branch is rebased onto current master so CI gets a fresh run. Replies are on the individual threads. On the one red check — **`test-flink-1 (flink2.1)` is not this PR.** It failed in `ITTestHoodieDataSource.testLookupJoin` with `Runtime Failed to fetch next result`, in `hudi-flink`: ``` [ERROR] Tests run: 264, Failures: 0, Errors: 1, Skipped: 1 -- in org.apache.hudi.table.ITTestHoodieDataSource [ERROR] ITTestHoodieDataSource.testLookupJoin:1263 » Runtime Failed to fetch next result ``` Three things place it outside this change: 1. This PR touches three files, all under `hudi-utilities/src/test/`. There is no path by which a `hudi-utilities` test-only change affects a `hudi-flink` integration test. 2. **The same branch, same code, passed `test-flink-1` five-for-five** in the earlier run (`30811001377`, 2026-08-03). Only the 2026-08-11 run failed, with nothing changed in between — so the failure is not deterministic. 3. `test-flink-1` is green on 11 other recent runs across the repo in the same window, including `master` itself. Azure also reports SUCCESS for the same head. I have deliberately not "fixed" anything for it — the honest read is a flaky Flink lookup-join test, and papering over it here would hide it. Worth its own issue if it recurs; happy to file one. One note for the record, since it cost me a detour and might catch someone else: `mvn compile -pl hudi-utilities` **without** a Spark profile fails on `KafkaAvroSchemaDeserializer.java:71` (`method does not override or implement a method from a supertype`) on plain master too — `confluent.version` 5.5.0 resolves differently, and the `deserialize(String, byte[], Schema)` overload is not on the supertype. With `-Dscala-2.12 -Dspark3.5` it compiles clean. Not a master breakage, just an invocation that needs the profile. -- 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]
