Waymark / Routes / materialize.com Create Materialize indexes to accelerate in-memory point lookups on a view
domain: materialize.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Identify the materialized view or source and the columns most frequently used in WHERE equality or join predicates. Run CREATE INDEX <index_name> ON <view_name> (<column1>, <column2>) in the cluster where the view is maintained. Use EXPLAIN SELECT ... to confirm that the query planner uses the index rather than a full scan. For default indexes (all key columns), use CREATE DEFAULT INDEX ON <view_name>. Check mz_indexes and mz_index_targets in the system catalog to confirm the index was created and is hydrated. Drop unused indexes to reduce memory pressure on the cluster. Known gotchas Indexes in Materialize consume cluster memory proportional to the indexed data; over-indexing large views can exhaust cluster resources. An index only accelerates queries routed to the cluster where it was created; cross-cluster queries do not benefit. Indexes on sources without a declared key may require explicit key columns; consult current docs for key inference rules.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp