[Feedback] Page: /api/latest/hypertable/add_reorder_policy/

[mikhail-sv]

Is it easy to find the information you need?

Yes

Are the instructions clear?

No

How could we improve the Timescale documentation site?

What does it mean?

chunks that are complete, and are no longer being written to

Chunks that are completely filled with data like all ids and all data points?
Please provide some examples or give an option to execute it as cronjob for example reorder_chunks every 1 month
Because right now the most clear and working solution would be to create a table last_reorder and write there last time table was reordered and check for last update time and launch an external worker like special pod in kubernetes or whatever

[github-actions]

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