-
Notifications
You must be signed in to change notification settings - Fork 300
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
[Backport 2.x] Disables custom serialization #3826
[Backport 2.x] Disables custom serialization #3826
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## 2.x #3826 +/- ##
============================================
- Coverage 64.90% 56.99% -7.92%
+ Complexity 3664 3158 -506
============================================
Files 292 292
Lines 20648 20652 +4
Branches 3402 3402
============================================
- Hits 13402 11771 -1631
- Misses 5563 7181 +1618
- Partials 1683 1700 +17
|
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.
#3789 has CI failures that need investigation, that should be resolved before we attempt to backport. @parasjain1 Please let us know what you discover
Signed-off-by: Paras Jain <parasjaz@amazon.com>
254c02b
to
7a8a671
Compare
Updated both the PRs. Will wait for CI tests to complete on the latest changes. |
One of the BWC tests failing due to the below error. 3 other are passing. I do not see any exceptions related to the serde change in the test logs.
One of the integration tests failing due to -
|
Signed-off-by: Paras Jain <parasjaz@amazon.com>
Looking at BWC failure:
|
} | ||
|
||
public static boolean shouldUseJDKSerialization(Version remoteVersion) { | ||
return !remoteVersion.equals(ConfigConstants.FIRST_CUSTOM_SERIALIZATION_SUPPORTED_OS_VERSION); |
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.
@parasjain1 Does this need to include 2.11.1 as well?
return !Set.of(Version.2_11_0, Version.2_11_1).contains(remoteVersion);
As with the original PR: Update 1/12/2024: For the time being, a majority of maintainers have voted in favor of keeping the feature as is (not disabling it). The fact that the feature does not work does not represent a good reason to remove it from the code. We have limited anecdotes about this causing issues and so we do not want to set a precedent of removing features which have bugs. We of course hope that this can be fixed but in the meantime will continue to ship with it as is. I am going to close this pull request given this decision but feel free to re-open it/keep discussing on it. This decision was reached by the maintainers as a group but does not mean it is set in stone. |
Description
Disables custom serialization
Backport of #3789
Issues Resolved
[List any issues this PR will resolve]
Is this a backport? If so, please add backport PR # and/or commits #
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.