-
Notifications
You must be signed in to change notification settings - Fork 42
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
chore: df 35 upgrade #2599
chore: df 35 upgrade #2599
Conversation
@@ -1,3 +1,7 @@ | |||
// allow deprecated items | |||
// TODO: fix the deprecation warnings with scalarUDF. | |||
#![allow(deprecated)] |
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.
This is bigger than just upgrading to the latest version. It doesn't hurt anything using the older way, so let's just follow up with this as part of #2490
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.
Generally this is fine, have two questions:
- is there anything that you're worried about that the tests wouldn't cover?
- should we tag the release before this is merged or do you think this is going to be safe to release without further testing?
no i think this is fine, the impact surface was much smaller than our last upgrade, and i'd be suprised if our slts missed anything major |
No description provided.