Skip to content
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

Deprecate LogicalPlan::head_output_expr #10024

Closed
wants to merge 1 commit into from

Conversation

alamb
Copy link
Contributor

@alamb alamb commented Apr 10, 2024

Which issue does this PR close?

Part of #8913

Rationale for this change

LogicalPlan::head_output_expr is unused, untested and redundant now that we have #8913

What changes are included in this PR?

  1. Deprecate LogicalPlan::head_output_expr
  2. Rewrite it to use the tree node API (by way of illustration to anyone else who might still use it)

Are these changes tested?

Are there any user-facing changes?

@github-actions github-actions bot added the logical-expr Logical plan and expressions label Apr 10, 2024
| LogicalPlan::DescribeTable(_)
| LogicalPlan::Unnest(_) => Ok(None),
}
let mut output = None;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am a big fan of the treenode API

@crepererum
Copy link
Contributor

I think clippy found a few users of the deprecated API. Might be worth to at least migrate the DF-internal users right away.

@alamb alamb marked this pull request as draft April 10, 2024 10:49
@alamb
Copy link
Contributor Author

alamb commented Apr 10, 2024

I didn't realize the function was actually used. I'll look into simply using the TreeNode API instead, rather than deprecating it

@alamb alamb closed this Apr 10, 2024
@alamb alamb deleted the alamb/no_head_output branch April 10, 2024 11:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
logical-expr Logical plan and expressions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants