fix: use source schema to find time column instead of projected schema #16
Conversation
This file contains 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
Rachelint
reviewed
Mar 5, 2024
Rachelint
pushed a commit
to apache/horaedb
that referenced
this pull request
Mar 6, 2024
## Rationale When time column is not in `select`, `extract_time_range` will not find time range of one query ## Detailed Changes - CeresDB/influxql#16 ## Test Plan CI
zealchen
pushed a commit
to zealchen/incubator-horaedb
that referenced
this pull request
Apr 9, 2024
## Rationale When time column is not in `select`, `extract_time_range` will not find time range of one query ## Detailed Changes - CeresDB/influxql#16 ## Test Plan CI
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See apache/horaedb#1445
Projected schema may not contain all column used in query, such as:
Only
ais in projected schema.