thinkharderdev opened a new pull request, #560:
URL: https://github.com/apache/arrow-ballista/pull/560
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #554
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
See issue for rationale
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
This is part 1 which creates a `ClusterState` interface for a higher-level
abstraction to manage executor resources. A default implementation is provided
which just uses the `StateBackendClient` for the underlying implementation so
functionally this should not change anything for existing users.
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
A new CLI config `-c/--cluster-backend` is available to set the backend for
`ClusterState` which will default to `Sled`. Right now there is no way to use a
separate Sled dir (or etcd cluster for that matter) for the regular
`StateBackendClient` and the `ClusterState` because I though that would be
weird use case and mostly just make things confusing.
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
No
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
