ToTime2, 3, & 4 should expect null values - #115
Open
bryantaustin13 wants to merge 4 commits into
Open
bryantaustin13 wants to merge 4 commits into
bryantaustin13 wants to merge 4 commits into
Conversation
brynrhodes
approved these changes
Jul 2, 2026
brynrhodes
approved these changes
Aug 20, 2026
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
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.
Based on the spec ToTime returns null when the expression contains an invalid time string. See:
cqlreference
"CQL supports time values in the range @t00:00:00.0 to @t23:59:59.999 with a step size of 1 millisecond."
&
logical spec
"For String values, the operator expects the string to be formatted using ISO-8601 time representation" and
"If the input string is not formatted correctly, or does not represent a valid time-of-day value, the result is null."