Hello Everyone, I’m experiencing strange behavior in StarRocks. In version 3.3, when I created a table with yearly range partitions, everything worked fine as long as no Materialized View (MV) was involved. However, after creating an MV that is partitioned by a date column, the script that still referenced the original base table (instead of the MV) started failing with the following error: Error Code: 1064 *StarRocks planner used a long time (3000 ms) in the memo phase. Possible reasons: 1. FE Full GC 2. Hive external table metadata fetch took too long 3. SQL is highly complex 4. You can try adjusting FE JVM config, retrying the query, or increasing the new_planner_optimize_timeout session variable.* If I modify the script to use the MV instead of the base table, it works perfectly. Additionally, if I change the base table partition type from range partitioning to date partitioning, queries on the base table starts failing with the same “3000 ms in memo phase” error—*even without creating any MV.* I’m confused about how partitions and MVs should work together. Do I need to define partitions on the base table, and under what circumstances should I use the MV?

Can you share how you create your table and your mv? Also can you run this and share the results

show tablets from <table or mv>;

show partitions from <table or mv>;

Here is all the Information.

Can you share the partitions in the mv? I see you are using `PARTITION BY `FullDate_CY`` in your mv. This potentially create a new partitions for every distinct date.