You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds the durable table that hydration episodes are recorded into, along with the
index that serves the question users ask of it, how long a given object took to
hydrate. Nothing writes the table yet.
The table is in `mz_internal` because its contents are best effort and its
`status` column will gain values as more hydration events become observable.
An episode is keyed by `(object_id, replica_id, installed_at)`, using the
replica-stamped installation time because it is stable across an environmentd
restart.
Contents are exempt from the bootstrap reset and from forced schema migrations,
since a sampled history cannot be rebuilt from anything else once it is gone.
Durability is best effort in both directions, and the assert added here is a
tripwire so that clearing the table is chosen rather than stumbled into.
Adding a builtin index changes the fingerprint of the `mz_indexes` materialized
view, which inlines the builtin index set as VALUES for exactly that reason, so
this also declares the required replacement migration step.
Ref: SQL-644
Copy file name to clipboardExpand all lines: doc/user/content/reference/system-catalog/mz_internal.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -688,6 +688,28 @@ The `mz_object_history` view enriches the [`mz_catalog.mz_objects`](/reference/s
688
688
|`created_at`|[`timestamp with time zone`]| Wall-clock timestamp of when the object was created. `NULL` for built in system objects. |
689
689
|`dropped_at`|[`timestamp with time zone`]| Wall-clock timestamp of when the object was dropped. `NULL` for built in system objects or if the object hasn't been dropped. |
690
690
691
+
## `mz_object_hydration_history`
692
+
693
+
The `mz_object_hydration_history` table records completed hydration of indexes and
694
+
materialized views, with one row for each time an object hydrated on a replica. Rows
695
+
are retained for 30 days, and `object_id`, `cluster_id`, and `replica_id` may name
696
+
objects that no longer exist.
697
+
698
+
Recording is best effort. Only successful hydration is recorded, an episode can be
699
+
missed if the object or its replica goes away before the episode is recorded, and a
700
+
schema change to this table in a future release may clear its contents.
0 commit comments