[Feedback] Page: /use-timescale/latest/continuous-aggregates/hierarchical-continuous-aggregates/

[aiman-saeed]

Is it easy to find the information you need?

None

Are the instructions clear?

None

How could we improve the Timescale documentation site?

There should be mention on this page about refresh policies of hierarchical-continuous-aggregates, how would a cagg bring its data, would it bring it recursively? Because that's how real-time aggregation would bring the data, and if there is no data it would bring from hypertable? There should be a clear mention that it does it this way. Rest is great, thank-you for awesomeness!!!

[github-actions[bot]]

Thank you for the report. We welcome documentation contributions!

• For information about how to propose a change, see the contributing guide in our GitHub repository.
• For information on style and word usage, see the style guide

[jonatas]

Thanks for the feedback, @aiman-saeed!

I see your point. We should make it clear that real time aggregates even hierarchical will make the recursive calls until it reaches the raw data. That's a great point!

[aiman-saeed]

1. Just to confirm, the refresh on a weekly data would recursively go down to the hourly data and lastly to the hypertable?

2. When it does this to refresh weekly bucket - would it also refresh the hourly and daily buckets ?

[jonatas]

With real time aggregation, you can check that the query will be something like:

select * from materialized_view_name
union all <caggs-query> where time > $cagg_watermark

Where the $cagg_watermark means the latest processing of the refresh. It understands where it stopped and get data newer than that.

You can check it yourself using \d+ <cagg-name> on psql.