fix: Fix the bug in parse date to int when year out of range #260
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… of range. Signed-off-by: FearfulTomcat27 <1471335448@qq.com>
JackieTien97
approved these changes
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request includes updates to the
DateUtilsclass to enhance date validation logic. The changes ensure that the year in the date expression falls within a valid range.Validation improvements:
java/tsfile/src/main/java/org/apache/tsfile/utils/DateUtils.java: Updated theparseDateExpressionToInt(String dateExpression)method to throw an exception if the year is greater than 9999.java/tsfile/src/main/java/org/apache/tsfile/utils/DateUtils.java: Updated theparseDateExpressionToInt(LocalDate localDate)method to throw an exception if the year is greater than 9999.