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

Upgrade arrow 430 #550

Closed
wants to merge 2 commits into from
Closed

Conversation

jimexist
Copy link
Member

Which issue does this PR close?

Closes #.

Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

@codecov-commenter
Copy link

Codecov Report

Merging #550 (ca2ce71) into master (8f4078d) will not change coverage.
The diff coverage is n/a.

❗ Current head ca2ce71 differs from pull request most recent head b99a237. Consider uploading reports for the commit b99a237 to get more accurate results
Impacted file tree graph

@@           Coverage Diff           @@
##           master     #550   +/-   ##
=======================================
  Coverage   76.09%   76.09%           
=======================================
  Files         156      156           
  Lines       27048    27048           
=======================================
  Hits        20581    20581           
  Misses       6467     6467           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8f4078d...b99a237. Read the comment docs.

Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I plan to release arrow 4.3 to crates.io tomorrow (process is underway -- see https://lists.apache.org/thread.html/r5bfdcf0e069b5df14477b1ac6cd3584e5ee0b0be2d0d4bd18db8f9ab%40%3Cdev.arrow.apache.org%3E)

Once I release to crates.io this change is not necessary (any local checkout will just need to do cargo update and will update to arrow 4.3.0) and other datafusion users can use whatever version of arrow that is in Cargo.lock

Sorry that this is confusing / slow.

@jimexist
Copy link
Member Author

I plan to release arrow 4.3 to crates.io tomorrow (process is underway -- see https://lists.apache.org/thread.html/r5bfdcf0e069b5df14477b1ac6cd3584e5ee0b0be2d0d4bd18db8f9ab%40%3Cdev.arrow.apache.org%3E)

Once I release to crates.io this change is not necessary (any local checkout will just need to do cargo update and will update to arrow 4.3.0) and other datafusion users can use whatever version of arrow that is in Cargo.lock

Sorry that this is confusing / slow.

it's okay not slow at all. was just trying to see if things would break. Thanks for the work of releasing!

@jimexist jimexist closed this Jun 13, 2021
@jimexist jimexist deleted the upgrade-arrow-430 branch June 13, 2021 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants