andygrove opened a new pull request, #970:
URL: https://github.com/apache/arrow-ballista/pull/970
# 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.
-->
N/A
# 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.
-->
Allow Python users to run SQL queries against a Ballista cluster.
```python
>>> from pyballista import SessionContext
>>> ctx = SessionContext("localhost", 50050)
>>> df = ctx.sql("SELECT 1")
>>> df.collect()
[pyarrow.RecordBatch
Int64(1): int64 not null
----
Int64(1): [1]]
```
The Python bindings in https://github.com/apache/arrow-ballista-python were
created by cloning the DataFusion Python bindings and then making some
modifications. This project has been unmaintained for around one year now.
This PR adds new Python bindings which depend on the `datafusion-python`
project rather than copying all of the code. I propose that we archive the old
repo.
This PR has minimal functionality and can run a `SELECT 1` query against a
Ballista cluster. I will follow up with more PRs to add context methods for
registering data sources.
This project will be versioned and released independently from the main
project and is not part of the default Cargo workspace, so will not get in the
way of development work.
# 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.
-->
New `pyballista` folder containing the new Python bindings.
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
No
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
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]
