Issues with detaching the tables beyond retention policy

[Durgamahesh671]

Hi @keithf4

"Does run_maintenance_proc cleanly detach tables beyond the retention policy on newer versions even running selects on tables beyond retention policy, so we don't need custom logic?
(expecting queue based detach)
Does 5.2.0 work well by detach tables on queue based approach?

[keithf4]

I'm not sure what you mean by queue based approach. The default operation for retention is to detach any table that contains data that is entirely outside the retention window. By default it only detaches the table, it does not drop it, so the data should not be visible to anyone querying the parent table. However, if they are querying directly from the child table, that would still be possible even after retention has detached it.

If you'd like the table dropped, or moved to another schema, see the retention_ options in the part_config table.

[keithf4]

Moving this issue to Q&A Discussion