You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess it's because of the time index for the metric is greptime_timestamp while the default time index for vector() is time
What did you expect to see?
.
What did you see instead?
Internal error during building DataFusion plan: No field named greptime_timestamp. Valid fields are .time, .greptime_value, .collector.
What operating system did you use?
macos
What version of GreptimeDB did you use?
0.11.2
Relevant log output and stack trace
{
"code": 3000,
"error": "Internal error during building DataFusion plan: No field named greptime_timestamp. Valid fields are .time, .greptime_value, .collector.",
"execution_time_ms": 0
}
The text was updated successfully, but these errors were encountered:
0neSe7en
changed the title
PromQL queries with binary operators and label_replace results error
PromQL queries with binary operators and vector(0) results error
Jan 17, 2025
yihong0618
added a commit
to yihong0618/greptimedb
that referenced
this issue
Jan 19, 2025
What type of bug is this?
Incorrect result
What subsystems are affected?
Query Engine
Minimal reproduce step
execute a PromQL like
vector(1) * metric
.I guess it's because of the time index for the metric is
greptime_timestamp
while the default time index forvector()
istime
What did you expect to see?
.
What did you see instead?
What operating system did you use?
macos
What version of GreptimeDB did you use?
0.11.2
Relevant log output and stack trace
The text was updated successfully, but these errors were encountered: