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

Update the continuous aggregate README #2147

Closed
erimatnor opened this issue Jul 28, 2020 · 0 comments · Fixed by #2405
Closed

Update the continuous aggregate README #2147

erimatnor opened this issue Jul 28, 2020 · 0 comments · Fixed by #2405

Comments

@erimatnor
Copy link
Contributor

There's a README describing the continuous aggregate implementation in tsl/src/continuous_agg/Readme.md that requires updates. It already seems out-of-date, and will be even more out-of-date with the new refresh API.

@erimatnor erimatnor added this to the 2.0.0 milestone Jul 28, 2020
@erimatnor erimatnor self-assigned this Sep 15, 2020
erimatnor added a commit to erimatnor/timescaledb that referenced this issue Sep 16, 2020
The README that gives an overview of the implementation of continuous
aggregates is updated to reflect changes to the feature.

Fixes timescale#2147
erimatnor added a commit to erimatnor/timescaledb that referenced this issue Sep 18, 2020
The README that gives an overview of the implementation of continuous
aggregates is updated to reflect changes to the feature.

Fixes timescale#2147
erimatnor added a commit to erimatnor/timescaledb that referenced this issue Sep 18, 2020
The README that gives an overview of the implementation of continuous
aggregates is updated to reflect changes to the feature.

Fixes timescale#2147
erimatnor added a commit that referenced this issue Sep 18, 2020
The README that gives an overview of the implementation of continuous
aggregates is updated to reflect changes to the feature.

Fixes #2147
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant