fix!: Fix LATERAL VIEW POSEXPLODE transpilation
#6844
+49
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6836
Hive hierarchy supports
LATERAL VIEW POSEXPLODEi.e an enumeratedEXPLODEwith the following semantics:poscolumn is 0-based and precedes the exploded valuesARRAYvsMAPinputAn example:
Currently, our transpilation towards Presto/Trino & DuckDB is broken because:
posis reversed andWITH ORDINALITYclause is 1-based:This PR fixes the transpilation by (1) reversing the columns to match the
posposition and (2) subtracting 1 from theWITH ORDINALITYcolumn:Docs
Spark / DBX POSEXPLODE | Spark / DBX LATERAL VIEW | DuckDB WITH ORDINALITY | Presto/Trino WITH ORDINALITY