Hi @cdn_yyz_yul ,

To me, this seems to be a dependency resolution issue, rather than "refresh compute semantics". As, DLT compiler is highly restrictive in terms of "query shape", and would quickly filter out any unsupported query, and fall-back to "FULL REFRESH" mode.

As for this unpredictability in different modes, it might be just due to processing timing issue, as you mentioned that final table is detached.

- Is the "final_result" table a materialized view as well?
- How do you read/refer to the tables produced by like file1/file2? Maybe if you can share a bit of code where you refer to your produced MVs, it would be helpful.