alamb commented on issue #22547: URL: https://github.com/apache/datafusion/issues/22547#issuecomment-4958342630
I recommend we backport these issues too (made with Claude) -- I can review later in the week Wrong results: 1. https://github.com/apache/datafusion/pull/22444 — IS TRUE in EliminateOuterJoin wrongly converts outer joins to inner joins (#22441); introduced by #21549. Empirically verified: 53.1.0 returns correct rows, 54.0.0 doesn't. 2. https://github.com/apache/datafusion/pull/23049 — sort-merge join semi/anti drops matches across pending outer batches (#23048); introduced by the SMJ bitwise-path rewrite #20806. 3. https://github.com/apache/datafusion/pull/22791 — NestedLoopJoin emits spurious NULL-padded unmatched-left rows with multiple probe partitions; introduced by #21448. 4. https://github.com/apache/datafusion/pull/22727 — anchored-regex simplification produces wrong results/errors on Utf8View and LargeUtf8 columns (#22726); introduced by #20581, which extended the rewrite to those types. 5. https://github.com/apache/datafusion/pull/22815 — approx_distinct over-counts Utf8View values (#22796); introduced by the inline-u128 hashing fast path in #21064. Panics: 6. https://github.com/apache/datafusion/pull/23277 — panic ("len is 0 but index is 0") ordering a parquet scan by a computed projection alias (#23219). The panicking code predates 53, but #21182 (sort pushdown phase 2) made it reachable in default configuration — queries that ran on 53.x panic on 54.0.0. Already on the release issue #22547. 7. https://github.com/apache/datafusion/pull/22950 — shared statistics cache reused across schemas for anonymous file scans → panic (#22935, reporter explicitly bisected to "regression between 53.1.0 and 54.0.0"); introduced by #20047. Queries that fail to plan: 8. https://github.com/apache/datafusion/pull/22915 — = ANY (SELECT ...) / <> ALL (SELECT ...) fail with "duplicate unqualified field name mark" (#22477); introduced by #21265. Empirically verified working on the published 53.1.0 crate. 9. https://github.com/apache/datafusion/pull/22552 — recursive CTE queries with certain nullability patterns now fail at execution (#22034); #21912 made nullability checking strict without fixing the schema derivation. Caveat from the first pass: the fix is invasive (adds a field to LogicalPlan::RecursiveQuery + proto changes). -- 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]
