Skip to content

Support Apache Arrow 19 #2782

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

Merged
merged 1 commit into from
Apr 22, 2025
Merged

Support Apache Arrow 19 #2782

merged 1 commit into from
Apr 22, 2025

Conversation

JoshMock
Copy link
Member

Apache Arrow 19.0.0 came out and is compatible with the client's usage. We want this project to be compatible with as many versions of Arrow as possible, to ensure it isn't interfering with existing Arrow usage in a project, so setting this to work with any 18.x or 19.x version.

@JoshMock JoshMock merged commit 821e77e into main Apr 22, 2025
26 checks passed
@JoshMock JoshMock deleted the arrow-19 branch April 22, 2025 15:11
Copy link
Contributor

The backport to 8.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.x 8.x
# Navigate to the new working tree
cd .worktrees/backport-8.x
# Create a new branch
git switch --create backport-2782-to-8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 821e77e7ad17e141eb9fca9330c74b57b6b2b1d7
# Push it to GitHub
git push --set-upstream origin backport-2782-to-8.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.x

Then, create a pull request where the base branch is 8.x and the compare/head branch is backport-2782-to-8.x.

Copy link
Contributor

The backport to 8.18 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.18 8.18
# Navigate to the new working tree
cd .worktrees/backport-8.18
# Create a new branch
git switch --create backport-2782-to-8.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 821e77e7ad17e141eb9fca9330c74b57b6b2b1d7
# Push it to GitHub
git push --set-upstream origin backport-2782-to-8.18
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.18

Then, create a pull request where the base branch is 8.18 and the compare/head branch is backport-2782-to-8.18.

Copy link
Contributor

The backport to 9.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.0 9.0
# Navigate to the new working tree
cd .worktrees/backport-9.0
# Create a new branch
git switch --create backport-2782-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 821e77e7ad17e141eb9fca9330c74b57b6b2b1d7
# Push it to GitHub
git push --set-upstream origin backport-2782-to-9.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.0

Then, create a pull request where the base branch is 9.0 and the compare/head branch is backport-2782-to-9.0.

JoshMock added a commit that referenced this pull request Apr 22, 2025
(cherry picked from commit 821e77e)
JoshMock added a commit that referenced this pull request Apr 22, 2025
(cherry picked from commit 821e77e)
JoshMock added a commit that referenced this pull request Apr 22, 2025
(cherry picked from commit 821e77e)
JoshMock added a commit that referenced this pull request Apr 22, 2025
JoshMock added a commit that referenced this pull request Apr 22, 2025
JoshMock added a commit that referenced this pull request Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant