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
Is your feature request related to a problem or challenge?
Is your feature request related to a problem or challenge?
I extracted this from apache#13651 so it was more visible
Part of apache#13648
Inspired by / copied from apache#13651 from @wiedld
During upgrade, downstream systems often experience issues due to implicit changes (not explicit API changes) of LogicalPlans that DataFusion code begins relying on, and which result in unintended consequences when upgrading to a new version of DataFusion (see apache#13525).
Describe the solution you'd like
The idea is to make the current implicit assumptions ("Invariants" in more formal language)( explict and automatically check them.
Examples of implicit assumptions:
Schema column names can't be repeated (this is explicitly mentioned on apache#13525)
Inputs to UnionExec must have the same schema
...
Describe alternatives you've considered
I like the approach @wiedld took in apache#13651 :
define the invariants
check the invariants for extensible interfaces (which may be user defined)
throw the error closer to the problem (rather than weird behavior later)
Additional context
Sub tasks:
Define infrastructure to check LP invariant. PR: apache#13651
Define infrastructure to check physical plan invariants: apache#13986
Define infrastructure for user-defined invariants. See issue: apache#14029
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem or challenge?
Is your feature request related to a problem or challenge?
I extracted this from apache#13651 so it was more visible
Part of apache#13648
Inspired by / copied from apache#13651 from @wiedld
During upgrade, downstream systems often experience issues due to implicit changes (not explicit API changes) of LogicalPlans that DataFusion code begins relying on, and which result in unintended consequences when upgrading to a new version of DataFusion (see apache#13525).
Describe the solution you'd like
The idea is to make the current implicit assumptions ("Invariants" in more formal language)( explict and automatically check them.
Examples of implicit assumptions:
Schema column names can't be repeated (this is explicitly mentioned on apache#13525)
Inputs to UnionExec must have the same schema
...
Describe alternatives you've considered
I like the approach @wiedld took in apache#13651 :
define the invariants
check the invariants for extensible interfaces (which may be user defined)
throw the error closer to the problem (rather than weird behavior later)
Additional context
Sub tasks:
Define infrastructure to check LP invariant. PR: apache#13651
Define infrastructure to check physical plan invariants: apache#13986
Define infrastructure for user-defined invariants. See issue: apache#14029
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: