Apache DataFusion Ballista 0.8.0 Changelog#

Implemented enhancements:

Executor should use all available cores by default #218
Update task status to the task job curator scheduler #179
update datafusion and arrow to 20.0.0 #176
No scheduler logs when deployed to k8s #165
Upgrade to DataFusion 11.0.0 #163
Better encapsulation for ExecutionGraph #149
A stage may act as the input of multiple stages #144
Executor Lost handling #143
Cancel a running query. #139
Ignore the previous job_id inside fill_reservations() #138
Normalize the serialization and deserialization places of protobuf structs #137
Remove revive offer event loop #136
Remove Keyspace::QueuedJobs #133
Spawn a thread for execution plan generation #131
Introduce CuratorTaskManager for make an active job be curated by only one scheduler #130
Using tokio tracing for log file #122
Ballista Executor report plan/operators metrics to Ballista Scheduler when task finish #116
Add timeout settings for Grpc Client #114
Add log level config in ballista #102
Use another channel to update the status of a task set for executor #96
Add config for concurrent_task in executor #94
Ballista should support Arrow FlightSQL #92
Why not include the ballista-cli in the member of workspace #88
Upgrade dependency of arrow-datafusion to commit d0d5564b8f689a01e542b8c1df829d74d0fab2b0 #84
Support sled path in config file. #79
Support for multi-scheduler deployments #39
Ballista 0.7.0 Release #126
Improvements to Ballista extensibility #8
Implement Python bindings for BallistaContext #15

Fixed bugs: