You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In datafusion/optimizer/src/optimizer.rs:271 when calling assert_schema_is_the_same prev_plan / new_plan are backwards. This causes an incorrect / confusing assert error, indicating the optimized plan is actually the original plan.
To Reproduce
Any optimization error that produces a schema change will reproduce this bug.
In this particular case, the root cause of the schema change dropping timezone metadata for timestamps somewhere in the Optimizer rule simplify_expressions. Fixing this bug will help find the root cause.
Expected behavior
The assert_schema_is_the_same error should report prev_plan / new_plan in the correct order.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
In datafusion/optimizer/src/optimizer.rs:271 when calling
assert_schema_is_the_same
prev_plan / new_plan are backwards. This causes an incorrect / confusing assert error, indicating the optimized plan is actually the original plan.To Reproduce
Any optimization error that produces a schema change will reproduce this bug.
In this particular case, the root cause of the schema change dropping timezone metadata for timestamps somewhere in the Optimizer rule
simplify_expressions
. Fixing this bug will help find the root cause.Expected behavior
The
assert_schema_is_the_same
error should report prev_plan / new_plan in the correct order.Additional context
No response
The text was updated successfully, but these errors were encountered: