Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #9294.
Rationale for this change
Documentation states that datafusion-cli can be installed through pip; however, that is not the case. This adds a workflow to deploy datafusion-cli (and only the CLI, not the python module) to PyPI , allowing installation using pip.
What changes are included in this PR?
This is meant to be a minimal CI, to be reviewed and edited as necessary (handle licensing, tag names, maybe maintainers prefer manual releases, etc)
CC @andygrove as he's involved in arrow-datafusion-python workflows and can have some comments.
A final note: builds for 32-bit systems fail because of
src/main.rs:304
which expects1 << 40
to be usize. This causes cargo to panic and abort builds.Are these changes tested?
You can try testing the deployment yourself using
pip install datafusion-cli
. I thought I changed the name and the repo to reference my fork, but apparently not.I'll remove it from PyPI once the PR is ready to merge, to be redeployed by the maintainers.
Are there any user-facing changes?
Should be able to use pip to install datafusion-cli