SkillVaultskills Browse all 500 skills

Search · Version 1.2.0 · Reviewed 2026-08-02

Search Index Migration Planner

Make a defensible decision about mapping migration and shadow-query validation with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Plans zero-downtime search-index migrations with versioned mappings, dual writes, backfills, shadow reads, relevance comparison, and alias cutover.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Mapping migration
  • Shadow-query validation
  • Alias cutover

How Search Index Migration Planner works

You provide

Schema, query plans, and the real access pattern

It inspects

Plan accuracy and lock behavior for mapping migration

It decides

A shadow-query validation change weighed against write cost

You verify

Re-measured plan with buffer reads and timing compared

What it checks first

Search Index Migration Planner plans zero-downtime search-index migrations with versioned mappings, dual writes, backfills, shadow reads, relevance comparison, and alias cutover. Use it when the work involves Mapping migration, Shadow-query validation, Alias cutover.

  1. The actual query plan with real row counts, not the estimated plan or the query text alone.
  2. Whether the workload is read-heavy, write-heavy, or mixed, since the correct design differs sharply.
  3. Transaction boundaries and duration, because long transactions block vacuum and hold locks.
  4. Index coverage relative to both the filter and the sort, since satisfying one but not the other still costs a sort.
  5. Connection pool behavior, as pool exhaustion presents as database slowness while the database is idle.

Failure modes it recognizes

  • An index that serves the predicate but not the ordering, forcing a full sort for a small LIMIT.
  • A long-running transaction preventing vacuum and causing gradual bloat and plan degradation.
  • Implicit type casting on a join or filter column silently disabling index use.
  • Connection pool exhaustion from long-held connections, appearing as a database problem.
  • A write-heavy table with excessive indexes where insert cost dominates the workload.
  • Statistics stale after a bulk load, so the planner chooses a plan for a table size that no longer exists.

Answers it will reject

  • Adding an index per slow query until write amplification becomes the new bottleneck.
  • Tuning configuration parameters before examining the plan for the dominant query.
  • Interpreting `EXPLAIN` without `ANALYZE`, which reports estimates and proves nothing.
  • Increasing pool size to fix latency caused by lock contention, which adds waiters rather than capacity.

Decision rules it applies

  • Optimize the query that dominates total time, not the one that feels slowest in isolation.
  • Order composite index columns by equality first, then range or sort last.
  • Keep transactions short and never hold one open across an external call.
  • Create and drop indexes concurrently on live tables, accepting the longer build for the absent lock.

Evidence it asks for

  • `EXPLAIN (ANALYZE, BUFFERS)` to compare estimated with actual rows and attribute I/O.
  • Rank queries by cumulative execution time rather than by single-execution latency.
  • Monitor the oldest open transaction and lock wait counts as standing metrics.

The method inside

  1. Inventory dependencies, compatibility constraints, and current behavior affecting mapping migration.
  2. Create reversible seams for shadow-query validation before changing the critical path.
  3. Sequence alias cutover into independently verifiable increments with explicit rollback points.
  4. Keep old and new paths observable until equivalence is proven; remove the fallback only after acceptance criteria pass.

Deliverables

  • Mapping migration assessment
  • Shadow-query validation decision and action plan
  • Alias cutover verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We need to change analyzers and mappings for a billion-document Elasticsearch index without downtime.

Expected output

Create a versioned index, dual-write new changes, backfill by stable partitions, replay missed updates, shadow production queries, compare recall and latency, then atomically switch the read alias with a rollback window...

Boundaries and compatibility

Ideal for

  • Mapping migration: produce a decision or artifact grounded in supplied evidence.
  • Shadow-query validation: produce a decision or artifact grounded in supplied evidence.
  • Alias cutover: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.