andygrove commented on issue #5569: URL: https://github.com/apache/datafusion-comet/issues/5569#issuecomment-5781384939
All three items are now fixed, though not in the one-pass-per-item shape this issue proposed. | Item | 4.0.4 | 4.1.3 | 4.2.0 | | --- | --- | --- | --- | | 1. Variant shredding suites | already clean | #5745 | #4950 | | 2. `having-and-order-by-recursive-type-name-resolution.sql` | n/a | #5755 | #4950 | | 3. Parquet V2 writer matrix + `DELTA_LENGTH_BYTE_ARRAY` | #5760 | #5760 | #4950 | The 4.0 and 4.1 halves landed on main between 2026-09-08 and 2026-09-09. The 4.2 half is in #4950 and is not yet merged, so this issue should close with that PR rather than now. One thing this issue predicted and that turned out to be worth recording: the reseed hazard is real, but it does not need a reseed to bite. `dev/diffs/4.2.0.diff` exists only on the #4950 branch, so none of #5745, #5755 or #5760 reached it, and merging main into that branch produced no conflict at any point -- the 4.2 diff simply sat at its 2026-08-31 state while the sibling diffs moved on. By the time it was checked, seven upstream commits to `4.1.3.diff` had accumulated. The general fix is to not leave a supported version's suite outside the automated tiers: #4950 now also moves Spark 4.2 into the nightly tier, since a diff is kept current as a side effect of its suite running. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
