You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@houqp: Thanks for the update. I am trying to build python wheel locally but I noticed in Cargo.toml file the dependency listed datafusion = { git = "https://github.com/apache/arrow-datafusion.git", rev = "4d61196dee8526998aee7e7bb10ea88422e5f9e1" }
It did not get updated. Will maturin develop pick up the latest datafusion code? Please, can you clarify it? Thanks again.
@houqp: Thanks for the clarification and quick turnaround fix. I verified your changes and found two issues.
the requirement.txt is locked to Python 3.8 version. I think, this file should not be checked in the source since the python development version could be different. In my case, it was python 3.7 version.
the requirement.txt is locked to Python 3.8 version.
The requirements.txt is supposed to work for all python versions supported by the python binding. if it's broken for python 3.7, could you file a separate issue with the error message? We can continue the troubleshooting there.
I would like to submit my changes as part of update datafusion to 5.1.0 for python binding #967 PR. Please, let me know.
That's great, I recommend you send a separate PR based off the branch in #967 for this, or collaborate on #969 to get that issue addressed.
@andygrove@alamb@Dandandan@jorgecarleitao@nevi-me given that we have had many major breaking changes merged in since the 5.x release, I am thinking maybe it's better to skip 5.1 and go 6.0 after #1010 gets merged. What do you think?
I think using 6.0 is a good idea. I also don't think we need to wait for #1010 to be merged for a release, if we need to get the python binding / cli out sooner
Thanks @alamb ! I just noticed I forgot to add (cd datafusion-cli && cargo publish) in the release doc, could you help run that command as well? I will send a PR to get the doc updated later today.
diff --git a/dev/release/README.md b/dev/release/README.md
index 2127dc23..73b3eb1a 100644
--- a/dev/release/README.md+++ b/dev/release/README.md@@ -304,7 +304,7 @@ PyPI, in order to conform to Apache Software Foundation governance standards.
First, download all official python release artifacts:
```shell
-svn co https://dist.apache.org/repos/dist/release/arrow/apache-arrow-datafusion-5.1.0-rc0/python ./python-artifacts+svn co https://dist.apache.org/repos/dist/release/arrow/arrow-datafusion-5.1.0/python ./python-artifacts
```
Use [twine](https://pypi.org/project/twine/) to perform the upload.
Good catch @kou , I will include that fix in my docs PR. The version diff is expected because we want them to be decoupled so we can release major version change in the python binding without forcing a major version bump in datafusion.
Thanks @alamb ! I just noticed I forgot to add (cd datafusion-cli && cargo publish) in the release doc, could you help run that command as well? I will send a PR to get the doc updated later today.
I tried to publish datafusion-cli and I got the following error. It looks like datafusion-cli relies on ballista somehow
(arrow_dev) alamb@MacBook-Pro:~/Downloads/apache-arrow-datafusion-6.0.0/datafusion-cli$ cargo publish
Updating crates.io index
warning: manifest has no description.
See https://doc.rust-lang.org/cargo/reference/manifest.html#package-metadata for more info.
Packaging datafusion-cli v5.1.0-SNAPSHOT (/Users/alamb/Downloads/apache-arrow-datafusion-6.0.0/datafusion-cli)
error: failed to prepare local package for uploading
Caused by:
failed to select a version for the requirement `ballista = "^0.6.0"`
candidate versions found which didn't match: 0.5.0, 0.3.0, 0.2.5, ...
location searched: crates.io index
required by package `datafusion-cli v5.1.0-SNAPSHOT (/Users/alamb/Downloads/apache-arrow-datafusion-6.0.0/datafusion-cli)`
Turns out I still can't upload datafusion-cli package:
(arrow_dev) alamb@MacBook-Pro:~/Downloads/apache-arrow-datafusion-6.0.0$ (cd datafusion-cli && cargo publish)
....
Finished dev [unoptimized + debuginfo] target(s) in 1m 20s
Uploading datafusion-cli v5.1.0-SNAPSHOT (/Users/alamb/Downloads/apache-arrow-datafusion-6.0.0/datafusion-cli)
error: failed to publish to registry at https://crates.io
Caused by:
the remote server responded with an error: invalid upload request: invalid length 7, expected at most 5 keywords per crate at line 1 column 3441
Activity
mmuru commentedon Sep 3, 2021
@houqp: Do we have an ETA on the python binding release? Thanks.
houqp commentedon Sep 3, 2021
@mmuru probably 2-3 weeks, need to get some legal issues resolved in #920 before we can cut a release tarball and start the voting process.
mmuru commentedon Sep 3, 2021
@houqp: Thanks for the update. I am trying to build python wheel locally but I noticed in Cargo.toml file the dependency listed
datafusion = { git = "https://github.com/apache/arrow-datafusion.git", rev = "4d61196dee8526998aee7e7bb10ea88422e5f9e1" }It did not get updated. Will maturin develop pick up the latest datafusion code? Please, can you clarify it? Thanks again.
houqp commentedon Sep 4, 2021
@mmuru it will not, I just sent #967 to handle the datafusion update.
mmuru commentedon Sep 5, 2021
@houqp: Thanks for the clarification and quick turnaround fix. I verified your changes and found two issues.
I would like to submit my changes as part of update datafusion to 5.1.0 for python binding #967 PR. Please, let me know.
houqp commentedon Sep 5, 2021
The requirements.txt is supposed to work for all python versions supported by the python binding. if it's broken for python 3.7, could you file a separate issue with the error message? We can continue the troubleshooting there.
That's great, I recommend you send a separate PR based off the branch in #967 for this, or collaborate on #969 to get that issue addressed.
mmuru commentedon Sep 6, 2021
@houqp: Sure, created
#975. Ping me if you need more information.houqp commentedon Sep 30, 2021
@andygrove @alamb @Dandandan @jorgecarleitao @nevi-me given that we have had many major breaking changes merged in since the 5.x release, I am thinking maybe it's better to skip 5.1 and go 6.0 after #1010 gets merged. What do you think?
alamb commentedon Sep 30, 2021
I think using 6.0 is a good idea. I also don't think we need to wait for #1010 to be merged for a release, if we need to get the python binding / cli out sooner
houqp commentedon Oct 2, 2021
sounds good, I think think I can try help push #873 to the finish line after you have arrow 6 released.
alamb commentedon Oct 2, 2021
It sounds like we are aiming to release arrow 6.0 in 2 weeks or so
[-]Release Datafusion 5.1.0[/-][+]Release Datafusion 6.0.0[/+]8 remaining items
houqp commentedon Nov 17, 2021
@jimexist we should be able to update datafusion-cli in homebrew as well.
jimexist commentedon Nov 17, 2021
Homebrew/homebrew-core#89562
alamb commentedon Nov 17, 2021
@houqp I will do so now. Thank you for all the work in this regard
houqp commentedon Nov 17, 2021
Thanks @alamb ! I just noticed I forgot to add
(cd datafusion-cli && cargo publish)in the release doc, could you help run that command as well? I will send a PR to get the doc updated later today.@andygrove @jorgecarleitao @kou @kszucs @xhochy we will need your help to publish the python binding to PyPI since only you are listed as maintainers of the PyPI package. The steps are documented at https://github.com/apache/arrow-datafusion/tree/master/dev/release#publish-on-pypi
xhochy commentedon Nov 17, 2021
I'd rather give more people access to PyPI ;)
kou commentedon Nov 17, 2021
I'm trying.
I found a typo in the document:
https://dist.apache.org/repos/dist/release/arrow/arrow-datafusion-6.0.0/python/ uses 0.4.0 not 6.0.0. Is it OK?
houqp commentedon Nov 17, 2021
+1 :D
Good catch @kou , I will include that fix in my docs PR. The version diff is expected because we want them to be decoupled so we can release major version change in the python binding without forcing a major version bump in datafusion.
kou commentedon Nov 17, 2021
OK. I've published them: https://pypi.org/project/datafusion/0.4.0/
I found one more typo:
houqp commentedon Nov 17, 2021
Thank you @kou ! I will include that fix in my docs PR as well :)
alamb commentedon Nov 18, 2021
Hi @houqp
I tried to publish
datafusion-cliand I got the following error. It looks like datafusion-cli relies on ballista somehowhouqp commentedon Nov 18, 2021
oh yeah, it supports ballista as a way to perform remote query execution. @alamb looks like we haven't published the ballista crates yet? could you do that first by following https://github.com/apache/arrow-datafusion/tree/master/dev/release#publish-on-cratesio?
alamb commentedon Nov 18, 2021
Done (updated instructions in #1331)
Turns out I still can't upload datafusion-cli package:
I will file a ticketTracked by #1332fix: Fix various memory leaks problems (apache#890)
Feature/instance udfs (apache#890)