Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EPIC: Deprecating, removing and making functionalities optional features #1067

Open
21 of 23 tasks
milenkovicm opened this issue Oct 11, 2024 · 1 comment
Open
21 of 23 tasks
Labels
enhancement New feature or request

Comments

@milenkovicm
Copy link
Contributor

milenkovicm commented Oct 11, 2024

As per our discussion in #1066 I'm opening this epic to break down PR #1066 to set of smaller chunks.

For could be contrib functionalities I suggest just to remove them at this point, who ever needs them can make contrib project from them

@milenkovicm milenkovicm added the enhancement New feature or request label Oct 11, 2024
milenkovicm added a commit to milenkovicm/arrow-ballista that referenced this issue Oct 11, 2024
milenkovicm added a commit to milenkovicm/arrow-ballista that referenced this issue Oct 11, 2024
it looks like not used anywhere.

Relates to: apache#1066 & apache#1067
milenkovicm added a commit to milenkovicm/arrow-ballista that referenced this issue Oct 11, 2024
andygrove pushed a commit that referenced this issue Oct 11, 2024
it looks like not used anywhere.

Relates to: #1066 & #1067
andygrove pushed a commit that referenced this issue Oct 11, 2024
milenkovicm added a commit to milenkovicm/arrow-ballista that referenced this issue Oct 12, 2024
milenkovicm added a commit to milenkovicm/arrow-ballista that referenced this issue Oct 12, 2024
As it may be useful I'd argue that it should not be
part of core ballista. We see in the community
caches build on top of object_store.

If functionality like this is needed it should be
implemented as scheduler-policy or similar.

Relates to: apache#1066 & apache#1067
@milenkovicm
Copy link
Contributor Author

@andygrove the other few PR will be pushed once we finish with current backlog, they may introduce merge conflicts

andygrove pushed a commit that referenced this issue Oct 12, 2024
As it may be useful I'd argue that it should not be
part of core ballista. We see in the community
caches build on top of object_store.

If functionality like this is needed it should be
implemented as scheduler-policy or similar.

Relates to: #1066 & #1067
milenkovicm added a commit to milenkovicm/arrow-ballista that referenced this issue Oct 15, 2024
- ballista.plugin_dir
- update to `actions/checkout@v4`

relates to apache#1067
andygrove pushed a commit that referenced this issue Oct 16, 2024
- ballista.plugin_dir
- update to `actions/checkout@v4`

relates to #1067
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant