-
Notifications
You must be signed in to change notification settings - Fork 578
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
build(deps): bump arrow-udf to use arrow 52 #18609
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
325bceb
to
2818887
Compare
# branch rw_patch | ||
icelake = { git = "https://github.com/risingwavelabs/icelake.git", rev = "db4868f9a5de8ff8f6c04ec4c203bcbe59564cbe", features = [ | ||
"prometheus", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed a new commit in icelake to pin arrow & opendal major version
9268e4f
to
99f942a
Compare
Is this going to supersede #17544 ? |
src/expr/impl/Cargo.toml
Outdated
# For arrow-udf-flight | ||
tonic = { version = "0.11", optional = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you keep TODO(http-bump)
so that we can easily find it?
This might solve a large pain point: Whenever we modify any entry in Cargo.toml, arrow will be affected. rust-lang/cargo#14115
99f942a
to
f2b1812
Compare
Signed-off-by: xxchan <xxchan22f@gmail.com>
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
This might solve a large pain point: Whenever we modify any entry in Cargo.toml, arrow will be affected (rust-lang/cargo#14115). Because arrow-udf doesn't use
>=
version any moreChecklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.