Skip to content

fix(spark): output columns of expand relation#310

Merged
Blizzara merged 1 commit intosubstrait-io:mainfrom
andrew-coleman:fix_expand
Oct 25, 2024
Merged

fix(spark): output columns of expand relation#310
Blizzara merged 1 commit intosubstrait-io:mainfrom
andrew-coleman:fix_expand

Conversation

@andrew-coleman
Copy link
Copy Markdown
Member

Fix the logic for deriving whether each output column of the expand relation is nullable or not.
If one or more of the projections can assign null to the column, then it must be defined as nullable.

Copy link
Copy Markdown
Contributor

@Blizzara Blizzara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, thanks!

@Blizzara
Copy link
Copy Markdown
Contributor

@andrew-coleman ah this has a conflict in the tests it enables, mind merging/rebasing main in? :)

Fix the logic for deriving whether each output column of the
expand relation is nullable or not.
If one or more of the projections can assign null to the column,
then it must be defined as nullable.

Signed-off-by: Andrew Coleman <andrew_coleman@uk.ibm.com>

# Conflicts:
#	spark/src/test/scala/io/substrait/spark/TPCDSPlan.scala
@Blizzara Blizzara merged commit 6413e55 into substrait-io:main Oct 25, 2024
@andrew-coleman andrew-coleman deleted the fix_expand branch October 25, 2024 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants