Skip to content

Commit 2b01631

Browse files
authored
chore(flags): drop leftover references to the retired async projection flag (#8320)
1 parent 5126dc6 commit 2b01631

2 files changed

Lines changed: 7 additions & 7 deletions

File tree

‎apps/sim/lib/knowledge/__integration__/knowledge-projection.integration.ts‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
/**
22
* The knowledge projector and the readers that must stay correct while it lags. A GitHub member
33
* source's document in a search index is changed by a writer in either projection mode —
4-
* synchronous, as every writer now is, or deferred, as writers of releases that carried the
5-
* `knowledge-async-projection` flag were, leaving only a mark — and search is checked before the
4+
* synchronous, as every writer now is, or deferred, as writers of earlier releases could be,
5+
* leaving only a mark — and search is checked before the
66
* projector runs: a revoked member is refused and a granted one is served, on the vector and
77
* keyword legs and under the source filter, and a disabled or deleted chunk is gone at once. The
88
* projector's own contract follows: it converges the rows and removes the mark, keeps a mark that

‎packages/db/knowledge-projection.ts‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ import type { Sql, TransactionSql } from 'postgres'
55
const logger = createLogger('KnowledgeProjection')
66

77
/**
8-
* The transaction setting that skips the synchronous projection triggers. No application writer
9-
* sets it: every writer's projection rows are written by those triggers in its own transaction.
10-
* Releases that carried the `knowledge-async-projection` flag set it to leave a chunk write's rows
11-
* to the projector, which is why a mark can still carry content to project. Either way the
12-
* triggers mark the document in `knowledge_projection_dirty`.
8+
* The transaction setting that skips the synchronous projection triggers. Only the projector sets
9+
* it: every other writer's projection rows are written by those triggers in its own transaction.
10+
* A mark can still carry content to project, because earlier releases also set it on chunk writes
11+
* to leave their rows to the projector. Either way the triggers mark the document in
12+
* `knowledge_projection_dirty`.
1313
*/
1414
const KNOWLEDGE_PROJECTION_MODE_SETTING = 'sim.projection_mode'
1515

0 commit comments

Comments
 (0)