From 8f300f0a96c9884d539632499245a49d2a8d98c7 Mon Sep 17 00:00:00 2001
From: Silvan <silvan.reusser@gmail.com>
Date: Wed, 17 Jul 2024 07:23:29 +0200
Subject: [PATCH] chore: set defaults for fields projections (#8311)

# Which Problems Are Solved

Bigger systems need to process many events during the initialisation
phase of the `eventstore.fields`-table. During setup these calls can
time out.

# How the Problems Are Solved

Changed the default behaviour of these projections to not time out and
increased the bulk limit.

(cherry picked from commit 6c1df830713891d06fcf66df133badee9d49bc45)
---
 cmd/defaults.yaml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/cmd/defaults.yaml b/cmd/defaults.yaml
index b4047ab5d1..c17b90cd86 100644
--- a/cmd/defaults.yaml
+++ b/cmd/defaults.yaml
@@ -231,6 +231,13 @@ Projections:
     custom_texts:
       TransactionDuration: 2s
       BulkLimit: 400
+    project_grant_fields:
+      TransactionDuration: 0s
+      BulkLimit: 2000
+    org_domain_verified_fields:
+      TransactionDuration: 0s
+      BulkLimit: 2000
+    
     # The Notifications projection is used for sending emails and SMS to users
     Notifications:
       # As notification projections don't result in database statements, retries don't have an effect