MaterializedView re-created on every migration loop; missing from remote_state.json

[cm-vgl-bee]

Summary

test_matview_agg_mv.zip

The Moose migration re-creates a MaterializedView on every run.

Steps To Reproduce:

1. Define a MaterializedView using an ARRAY JOIN with tuple projections and stateful functions
2. trigger a migration

See attached example.

Expected result

The migration completes and subsequent runs recognize that no schema changes are needed.

Actual result

The MaterializedView is re-created on every run. The CLI states "Migration completed successfully" and the view is successfully created in the ClickHouse database, but it is not captured in the remote_state.json.

Additional information

Moose CLI Version: 0.6.533

OS and version: node:20-bookworm docker container

[coderabbitai]

🔗 Related PRs

#3377 - update mv docs [merged]
#3929 - Bug fix: backtick we're stripped inside materialized view (and regular view) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!