ContinueAsNew is able to reclaim rows in the History table, ensuring that an eternal orchestration doesn't create an infinite history. However, the SQL storage logic doesn't correctly clean up the dt.Payloads table when doing ContinueAsNew.
Here's a screenshot showing the results of the Orchestrations.ContinueAsNew integration test. As can be seen, there is a row in the dt.Payloads table for every input.
The expected behavior is that there is a row only for the currently valid inputs that have corresponding references in the dt.History table. Otherwise, ContinueAsNew effectively results in an unlimited number of orphaned dt.Payloads rows.
ContinueAsNew is able to reclaim rows in the History table, ensuring that an eternal orchestration doesn't create an infinite history. However, the SQL storage logic doesn't correctly clean up the
dt.Payloadstable when doing ContinueAsNew.Here's a screenshot showing the results of the Orchestrations.ContinueAsNew integration test. As can be seen, there is a row in the
dt.Payloadstable for every input.The expected behavior is that there is a row only for the currently valid inputs that have corresponding references in the
dt.Historytable. Otherwise, ContinueAsNew effectively results in an unlimited number of orphaneddt.Payloadsrows.