Move intervalToNanos out of the Calcite files and into our parser utils functions #120
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.
Changes included in this PR
Changes to
SqlParserUtil.java
should only be those breaking changes that we need to back port into importing Calcite (and should only be done when we do not actively include all uses of the file already in our source code). SinceintervalToNanos
, which is meant to replace theintervalToMilli
in Calcite requires a new function signature, every usage must exist inside our source code, so it should existing our extension files.Ideally in the future we could also remove
SqlParserUtil
in general, but right now we need the remaining changes to ensure we get some default precisions because of its reuse in the validator.Testing strategy
User facing changes
Checklist
[run CI]
in your commit message.