Is your feature request related to a problem or challenge? Please describe what you are trying to do.
On the road to library transition I would like to expose more configuration (DataFusion specific) which user can tune. This would enable us to remove hard coded object stores, codecs, configuration extension, functions ...
Describe the solution you'd like
I would like to expose additional method in executor/src/standalone.rs:
And optional parameter in executor/src/executor_process.rs:
pub struct ExecutorProcessConfig {
...
/// SessionState which will be used to configure executor
/// if not provided system will configure itself from
/// sensible defaults
pub session_state: Option<SessionState>,
}
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Follow up commit would remove with_object_store_registry and BallistaObjectStoreRegistry giving user ability to plug their own and removing chunk of code from maintenance.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
On the road to library transition I would like to expose more configuration (DataFusion specific) which user can tune. This would enable us to remove hard coded object stores, codecs, configuration extension, functions ...
Describe the solution you'd like
I would like to expose additional method in
executor/src/standalone.rs
:And optional parameter in
executor/src/executor_process.rs
:Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context
with_object_store_registry
andBallistaObjectStoreRegistry
giving user ability to plug their own and removing chunk of code from maintenance.depends on #1096