Hello, I have a question regarding partition retention behavior when using asynchronous materialized views in StarRocks. I created an asynchronous MV based on a source table, and I’ve observed that the MV partitions are being deleted according to the TTL defined on the source table partitions. My goal is to keep the source table’s TTL short while retaining the MV partitions for a longer duration. However, even after applying the following settings, the historical MV partitions continue to be removed:

"auto_refresh_partitions_limit" = "-1",
"partition_ttl" = "30 DAY",
"session.dynamic_overwrite" = "true",
"partition_ttl_number" = "-1",

For reference, the source table’s TTL is currently set to 2 hours, which results in both the source table and the MV retaining partitions for only 2 hours. Is there a way to configure the MV so that its partitions are retained independently of the source table’s TTL policy? Thank you for your time and support.

Did you ever find a work around to this? I have the same requirements, and am trying to figure out how to fix