Clarify that we mark as outliers because we don't have any state for …

…them (#12345) As discussed at #12179 (comment)
matrix-org · Apr 6, 2022 · 3500626 · 3500626
1 parent f931c06
commit 3500626
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/changelog.d/12345.doc b/changelog.d/12345.doc
@@ -0,0 +1 @@
+Updates to the Room DAG concepts development document to clarify that we mark events as outliers because we don't have any state for them.
diff --git a/docs/development/room-dag-concepts.md b/docs/development/room-dag-concepts.md
@@ -39,7 +39,8 @@ yet correlated to the DAG.
 Outliers typically arise when we fetch the auth chain or state for a given
 event. When that happens, we just grab the events in the state/auth chain,
 without calculating the state at those events, or backfilling their
-`prev_events`.
+`prev_events`. Since we don't have the state at any events fetched in that
+way, we mark them as outliers.
 
 So, typically, we won't have the `prev_events` of an `outlier` in the database,
 (though it's entirely possible that we *might* have them for some other
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		Updates to the Room DAG concepts development document to clarify that we mark events as outliers because we don't have any state for them.