Switch back to SimpleDateFormat from DateTimeFormatter and use ThreadLocal to achieve thread safety instead #14753
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DateTimeFormatter
which isn't backward compatible with the olderSimpleDateFormat
. Fix JDBC date time parsing issue #14739 attempted to fix some of the incompatibilities but there will always be some edge cases that aren't covered and it is critical to maintain backward compatibility for clients.SimpleDateFormat
but withThreadLocal
instead to achieve thread safety. This is more expensive since each thread would need to allocate an instance of SDF but is necessary for thread safety and correctness (as can be demonstrated from the tests added earlier).