EPIC: Deprecating, removing and making functionalities optional features #1067
Description
As per our discussion in #1066 I'm opening this epic to break down PR #1066 to set of smaller chunks.
- Remove Ballista python #1069 - datafusion python is the main effort, we should focus making it run on ballista
- Remove helm from supported code #1071- this can be contrib project
- Remove CI folder #1074 - ci works without it, could not relate content to anything in the repo
- Remove plugin subsystem #1070 - never finalized, dangling code
- Remove cache functionality #1076- this can be a contrib project, we could cover it with pluggable scheduler strategies
- Remove HDFS support ... #1073 - library too old, there are newer library to be used
- Remove UI #1072 - can be a contrib project
- Promote keda and flight-sql to optional features #1079
- Make rest-api optional feature ... #1084
- Remove key-value stores for scheduler persistence #1077 - only memory store remains, we may want to take different approach, like checkpointing or similar
- Reorganise and remove dependencies #1078
- Code cleanup, move examples, remove unused files #1075
- Update to datafusion 42 ... #1080
- fix issue with not building python package ... #1085
- Update and move deps to workspace #1109
- another round of code cleanup ... #1089
- Deprecate
BallistaContext#1103 & DeprecateBallistaContext#1102 - Remove build-in object store registry #1114
- Trim down
BallistaConfig#1104 - Update Documentation with
SessionContextExt#1105 - Ballista proto cleanup #1110
- Decommission
BallistaContext#1119 (depends on: Ballista Python Update #1091, added a BallistaContext to ballista to allow for Remote or standalone #1100, and previous)
For could be contrib functionalities I suggest just to remove them at this point, who ever needs them can make contrib project from them