JingsongLi opened a new pull request, #1292:
URL: https://github.com/apache/paimon-rust/pull/1292

   ### Purpose
   
   Closes #1284.
   
   DataFusion rejects LATERAL VIEW. A correlated UNNEST subquery is 
insufficient because the native physical planner cannot execute the projected 
outer reference.
   
   ### Brief change log
   
   - Support explode/posexplode and outer variants for arrays/maps with 
zero-based positions and exact empty/NULL behavior.
   - Use a relation-planner extension to plan the parent input and native 
list/struct UNNEST without correlated physical expressions or collecting the 
parent.
   - Preserve aliases, joins, chained generators, set-operation branches and 
portable persistent-view SQL; compensate for the pinned parser's optional-alias 
clause handling.
   
   ### Tests
   
   - Regression coverage: Array/Map values, NULL and empty collections, NULL 
elements, empty parent inputs, map defaults, quoted and explicit aliases, 
joins/duplicate rows, chained generators, UNION, dictionary collection/value 
nulls, and default-alias ORDER/LIMIT/OFFSET/QUALIFY boundaries.
   - Reproduced the missing behavior on the original main before implementation.
   - Passed `cargo test --locked -p paimon-datafusion --all-targets -- 
--test-threads=4` on this independent branch with Rust 1.95.0, `TZ=UTC` and 
`RUST_MIN_STACK=16777216`.
   - Passed `cargo +1.98.0 clippy --locked --no-deps -p paimon-datafusion 
--all-targets -- -D warnings`, formatting and `git diff --check`.
   - Reviewed repeatedly for SQL semantics, parser/type boundaries and 
regression quality; fixed the discovered alias, set-operation and 
default-column parsing cases.
   
   ### API and Format
   
   Adds SQLContext SQL capabilities. No storage-format or Rust public API 
changes.
   
   ### Documentation
   
   Documented syntax, type/null/error behavior and supported limits in 
`docs/src/sql.md`.
   


-- 
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]

Reply via email to