We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Move some rules and code into Analyzer
No response
The text was updated successfully, but these errors were encountered:
This is a very important feature. 🪜
Moving TypeCoercion into pre-optimizer phase would allow to avoid "Mismatch between schema and batches", like #5733 (and possibly #5695).
TypeCoercion
TypeCoercion being an optimizer is a broken concept - because optimizers cannot change the final schema of the logical plan.
What is more, Expr::Case has an assumption, that all inputs are already coerced.
Expr::Case
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem or challenge?
Describe the solution you'd like
Move some rules and code into Analyzer
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: