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? Please describe what you are trying to do.
The logic to optimize a LogicalPlan currently lives on SessionContext. This creates a couple of problems:
Forces query_execution_start_time to be stored on SessionState when it is a per-query property
DataFrame ends up calling back to SessionContext in order to optimize its plans, creating circular coupling between them
Describe the solution you'd like
I originally thought we might need to introduce a new per-query container, but it turns out DataFrame already fits this role nicely, especially following the changes in #4624.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
The logic to optimize a
LogicalPlan
currently lives onSessionContext
. This creates a couple of problems:query_execution_start_time
to be stored onSessionState
when it is a per-query propertyDataFrame
ends up calling back toSessionContext
in order to optimize its plans, creating circular coupling between themDescribe the solution you'd like
I originally thought we might need to introduce a new per-query container, but it turns out
DataFrame
already fits this role nicely, especially following the changes in #4624.Describe alternatives you've considered
Additional context
#4621 #4622
The text was updated successfully, but these errors were encountered: