-
Notifications
You must be signed in to change notification settings - Fork 2.3k
feat: switch VirtualTable producer to use expressions field instead of deprecated values #23672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
eliot1480
wants to merge
3
commits into
apache:main
Choose a base branch
from
eliot1480:remove-usages-of-deprecated-virtualtable-values-field
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -148,19 +148,45 @@ pub async fn from_read_rel( | |
| let values = if !vt.expressions.is_empty() { | ||
| let mut exprs = vec![]; | ||
| for row in &vt.expressions { | ||
| if row.fields.len() != substrait_schema.fields().len() { | ||
| return substrait_err!( | ||
| "Field count mismatch: expected {} fields but found {} in virtual table row", | ||
| substrait_schema.fields().len(), | ||
| row.fields.len() | ||
| ); | ||
| } | ||
|
|
||
| let mut row_exprs = vec![]; | ||
| let mut name_idx = 0; | ||
| for expression in &row.fields { | ||
| let expr = consumer | ||
| .consume_expression(expression, &substrait_schema) | ||
| .await?; | ||
| let expr = match expression.rex_type.as_ref() { | ||
| Some(substrait::proto::expression::RexType::Literal(lit)) => { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The first questions that readers might have is: Why does the |
||
| name_idx += 1; // top-level names are provided through schema | ||
| Expr::Literal( | ||
| from_substrait_literal( | ||
| consumer, | ||
| lit, | ||
| &named_struct.names, | ||
| &mut name_idx, | ||
| )?, | ||
| None, | ||
| ) | ||
|
eliot1480 marked this conversation as resolved.
|
||
| } | ||
| _ => { | ||
| name_idx += 1; // top-level names are provided through schema | ||
| consumer | ||
| .consume_expression(expression, &substrait_schema) | ||
| .await? | ||
| } | ||
| }; | ||
| row_exprs.push(expr); | ||
| } | ||
| // For expressions, validate against top-level schema fields, not nested names | ||
| if row_exprs.len() != substrait_schema.fields().len() { | ||
|
|
||
| if name_idx != named_struct.names.len() { | ||
| return substrait_err!( | ||
| "Field count mismatch: expected {} fields but found {} in virtual table row", | ||
| substrait_schema.fields().len(), | ||
| row_exprs.len() | ||
| "Names list must match exactly to nested schema, but found {} uses for {} names", | ||
| name_idx, | ||
| named_struct.names.len() | ||
| ); | ||
| } | ||
| exprs.push(row_exprs); | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both branches increment
name_idxby 1. I think we can extract that out out before the match and expand on the comment with something liketo provide a bit more context about what is happening.