-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[fix](gson) Fix Expr deserialize compatibility #38799
Conversation
Since GsonBuilder.create() adds all registered factories to GSON in reverse order, and ExprAdapterFactory is registered before the RuntimeTypeAdapterFactory for Expr, ExprAdapterFactory will not be executed. This PR adjusts their registration order. Now, it will first check in ExprAdapterFactory whether to use the pre-134 deserialize method, and then attempt to use the RuntimeTypeAdapterFactory for Expr.class.
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 41893 ms
|
TPC-DS: Total hot run time: 169426 ms
|
ClickBench: Total hot run time: 30.24 s
|
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.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
Since GsonBuilder.create() adds all registered factories to GSON in reverse order, and ExprAdapterFactory is registered before the RuntimeTypeAdapterFactory for Expr, ExprAdapterFactory will not be executed. This PR adjusts their registration order. Now, it will first check-in ExprAdapterFactory whether to use the pre-134 deserialize method and then attempt to use the RuntimeTypeAdapterFactory for Expr.class.
Since GsonBuilder.create() adds all registered factories to GSON in reverse order, and ExprAdapterFactory is registered before the RuntimeTypeAdapterFactory for Expr, ExprAdapterFactory will not be executed.
This PR adjusts their registration order. Now, it will first check-in ExprAdapterFactory whether to use the pre-134 deserialize method and then attempt to use the RuntimeTypeAdapterFactory for Expr.class.