This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Use StringUtils instead of NumberUtils to check timestamp string #360
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.
Issue #:
Fixes #359
Description of changes:
This change updates a check where we used
NumberUtils.isCreatable(timestamp);
toStringUtils.isNumeric(timestamp);
The check we want to do is that the value we received from the writer is actually an epoch which is checked more strongly with the
.isNumeric()
check than.isCreatable()
as the latter allows other forms of numbers(signed, hexadecimal, scientific notation, decimals) as valid numbers.Removes some unused imports as well.
Tests:
build passes.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.