-
Notifications
You must be signed in to change notification settings - Fork 882
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
Improve the error message when a time_bucket with offset/origin parameter is used with continuous aggregates #5828
Labels
Comments
lkshminarayanan
added
bug
continuous_aggregate
low-hanging-fruit
Label for issues that are easy to implement
labels
Jun 28, 2023
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Mar 29, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Mar 30, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Apr 2, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Apr 2, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Apr 2, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Apr 4, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Apr 5, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
jnidzwetzki
added a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Apr 5, 2024
So far, we allowed only CAggs without origin or offset parameters in the time_bucket definition. This commit adds support for the remaining time_bucket variants. Fixes timescale#2265, Fixes timescale#5453, Fixes timescale#5828
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What type of bug is this?
Other
What subsystems and features are affected?
Continuous aggregate
What happened?
Using time_bucket with origin/offset parameters in a continuous aggregate is currently not supported. (Refer to #2265 for further discussion on this.) When such an attempt is made by the user, the following error is thrown :
continuous aggregate view must include a valid time bucket function
, which is misleading as the time_bucket with an offset/origin parameter is a valid function outside the context of a continuous aggregate. A better error likecontinuous aggregate view doesn't support time bucket functions with origin/offset parameters
must be thrown instead for these cases.TimescaleDB version affected
2.11.0
PostgreSQL version used
15.3
What operating system did you use?
Ubuntu
What installation method did you use?
Source
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: