AuroraMeter.Migration.BackfillIncompleteError exception (Aurora Meter v1.0.0)

Raised by core schema version 8 while any aurora_meter_events row still has a null event_id.

Version 8 promotes event_id to NOT NULL behind a unique index on (tenant_key, event_id). Both need every row to carry an identity, which for rows written by 0.4.x is given by mix aurora_meter.events.backfill.

A non-zero count after a completed backfill means an 0.4.x node is still writing durable events through AuroraMeter.track/4. That is the one quiescence point in the V1 upgrade: stop those writers, run the backfill again, then run version 8. Refusing is the safe failure; a partial index would not be.

Summary

Types

t()

Types

t()

@type t() :: %AuroraMeter.Migration.BackfillIncompleteError{
  __exception__: term(),
  message: String.t(),
  remaining: non_neg_integer()
}