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
Copy file name to clipboardExpand all lines: doc/01_Installation/02_Upgrade.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,8 @@
3
3
Following steps are necessary during updating to newer versions.
4
4
5
5
## Upgrade to 2.2.0
6
-
- Added `trackTotalHits` parameter to `DefaultSearchService` and `SearchExecutionService`. The default value is true, which means that total hits will always be computed accurately, even if they exceed the search engines threshold for accurate hit calculation. Change this parameter to `null`, to use the default threshold, pass an integer value to set a specific one.
6
+
-[Indexing] Added `id` column as new primary key to `generic_data_index_queue`. Please make sure to execute migrations.
7
+
-[Searching] Added `trackTotalHits` parameter to `DefaultSearchService` and `SearchExecutionService`. The default value is true, which means that total hits will always be computed accurately, even if they exceed the search engines threshold for accurate hit calculation. Change this parameter to `null`, to use the default threshold, pass an integer value to set a specific one.
Copy file name to clipboardExpand all lines: doc/02_Configuration/03_Index_Management.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,6 +69,27 @@ pimcore_generic_data_index:
69
69
max_batch_size: 400
70
70
```
71
71
72
+
#### Related elements
73
+
74
+
The indexing queue is automatically populated whenever an element undergoes an update operation. This process includes not only the modified element itself but also any related elements. By default, this indexing occurs asynchronously through Symfony Messenger.
75
+
76
+
For scenarios requiring immediate processing, you can temporarily switch to synchronous mode by utilizing the `SynchronousProcessingRelatedIdsServiceInterface`.
| `disable()` | Reverts to asynchronous processing mode |
84
+
| `isEnabled()` | Returns the current processing mode status |
85
+
86
+
:::info
87
+
88
+
Currently the `SynchronousProcessingRelatedIdsServiceInterface` interface does not influence the behavior of delete operations. They are always processed synchronously.
89
+
90
+
:::
91
+
92
+
72
93
### Repairing Indices
73
94
74
95
Sometimes it might be needed to delete and recreate the index from the Pimcore database
0 commit comments