@remit/search-index-worker 0.0.15 → 0.0.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/search-index-worker",
-  "version": "0.0.15",
+  "version": "0.0.16",
   "type": "module",
   "main": "dist/index.js",
   "exports": {

package/src/consumer.ts

@@ -50,10 +50,9 @@ export interface SqsConsumerConfig {
  * via `processBatch` (a batch of one) — the same per-message logic the AWS
  * Lambda handler runs, reused so the two deployment shapes (Lambda event
  * source mapping vs. a long-running container/pm2 process) share one
- * indexing implementation. Used by the Postgres-parity stack, where the
- * search-index queue has no Lambda event source; `remit-pg-index-worker`
- * only relays committed outbox events onto this queue (the producer side —
- * see its `worker.ts`), it does not consume them.
+ * indexing implementation. Used by the self-host stack, where the search-index
+ * queue has no Lambda event source: the outbox drain relays committed events
+ * onto this queue (the producer side) and this consumer takes them off it.
  *
  * A message is deleted only when `processBatch` reports no failure for it;
  * a failure leaves it on the queue so its visibility timeout lapses and SQS

package/src/data-ports.ts

@@ -17,11 +17,10 @@ export interface SearchIndexDataPorts {
 	 * one — this hook is `undefined` there, and the handler uses the message's
 	 * own `accountId` unchanged (see `prepareUpsert` in handler.ts).
 	 *
-	 * The Postgres outbox trigger fires from a plain `message_id`, so the pg
-	 * relay (`remit-pg-index-worker`) has no accountId to attach; this hook
-	 * derives it from the message's mailbox at consume time instead. Returns
-	 * null when the mailbox can't be resolved (the message is skipped, not
-	 * retried — see handler.ts).
+	 * The outbox carries a plain `message_id`, so the relational drain has no
+	 * accountId to attach; this hook derives it from the message's mailbox at
+	 * consume time instead. Returns null when the mailbox can't be resolved (the
+	 * message is skipped, not retried — see handler.ts).
 	 */
 	resolveAccountId?: (messageId: string) => Promise<string | null>;
 }

package/src/handler.ts

@@ -86,9 +86,8 @@ const deleteMessage = async (
 // upsert per message means a record S3 Vectors rejects (e.g. a metadata
 // ValidationException) dead-letters on its own — its siblings in the
 // batch still index instead of retrying forever behind a poison record.
-// Exported so the long-running Postgres consumer (`consumer.ts`) can
-// process one message at a time outside the Lambda batch shape, reusing
-// this exact logic.
+// Exported so the long-running consumer (`consumer.ts`) can process one
+// message at a time outside the Lambda batch shape, reusing this exact logic.
 export const upsertMessage = async (
 	message: Extract<ParsedQueueMessage, { kind: "upsert" }>,
 	services: Services,