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

Mismatched interval in description and generated sql for single-groupy-X-X-X series #214

Open
JackieTien97 opened this issue Nov 23, 2022 · 0 comments

Comments

@JackieTien97
Copy link

In the descriptions of README for single-groupy-X-X-X, it says that the group by time interval is every 5 mins, e.g.
Simple aggregrate (MAX) on one metric for 1 host, every 5 mins for 1 hour for single-groupby-1-1-1.
However, in the generated sql for InfluxDB and TimescaleDB(I just checked these two, don't whether others are mismatched):

Sql generated for single-groupby-1-1-1

InfluxDB

SELECT max(usage_user) from cpu where (hostname = 'host_249') and time >= '2016-01-03T12:26:46Z' and time < '2016-01-03T13:26:46Z' group by time(1m)

TimescaleDB

SELECT time_bucket('60 seconds', time) AS minute,
        max(usage_user) as max_usage_user
        FROM cpu
        WHERE tags_id IN (SELECT id FROM tags WHERE hostname IN ('host_249')) AND time >= '2016-01-03 12:26:46.646325 +0000' AND time < '2016-01-03 13:26:46.646325 +0000'
        GROUP BY minute ORDER BY minute ASC
citrusreticulata added a commit to citrusreticulata/tsbs that referenced this issue Nov 27, 2022
for GroupByTime use 1min, fix issues timescale#214
IoTDB is same with InfluxDB and TimescaleDB now。
And that meas the behavior of IoTDB single-group-by queries is NOT same with README, but is same with other databases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant