Is your feature request related to a problem or challenge? Please describe what you are trying to do.
As we want to reduce code which is maintained by ballista, would like to propose deprecate for removal BallistaContext.
Describe the solution you'd like
With introduction of SessionContextExt I would like to propose to deprecate BallistaContext as SessionContextExt provides same functionality with possibility to reuse code from DataFusion and DataFusion Python.
At the initial phase, I propose to mark the struct as deprecated and keep it until we get Ballista Python migrated to SessionContext. Once we migrate all relevant code to SessionContextExt all relevant code to be removed.
I would also suggest not to keep interface stability while in this phase and continue evolve and remove dependant interfaces.
Describe alternatives you've considered
Additional context
BallistaContext will be deprecated util we manage to move all other code depending on it to SessionContext
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
As we want to reduce code which is maintained by ballista, would like to propose deprecate for removal
BallistaContext.Describe the solution you'd like
With introduction of
SessionContextExtI would like to propose to deprecateBallistaContextasSessionContextExtprovides same functionality with possibility to reuse code from DataFusion and DataFusion Python.At the initial phase, I propose to mark the struct as deprecated and keep it until we get Ballista Python migrated to
SessionContext. Once we migrate all relevant code toSessionContextExtall relevant code to be removed.I would also suggest not to keep interface stability while in this phase and continue evolve and remove dependant interfaces.
Describe alternatives you've considered
Additional context
BallistaContextwill be deprecated util we manage to move all other code depending on it toSessionContextBallistaContextto be removed in subsequent PR.