Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PromQL queries with binary operators and vector(0) results error #5392

Open
0neSe7en opened this issue Jan 17, 2025 · 1 comment · May be fixed by #5398
Open

PromQL queries with binary operators and vector(0) results error #5392

0neSe7en opened this issue Jan 17, 2025 · 1 comment · May be fixed by #5398
Labels
C-bug Category Bugs

Comments

@0neSe7en
Copy link

0neSe7en commented Jan 17, 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.

TQL EVAL (1737086400, 1737107500, '10s') vector(1) * host_cpu_seconds_total

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
}
@0neSe7en 0neSe7en added the C-bug Category Bugs label Jan 17, 2025
@0neSe7en 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
@yihong0618
Copy link
Contributor

try to close in #5398

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category Bugs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants