-
Notifications
You must be signed in to change notification settings - Fork 139
cds 9: task queue #1790
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cds 9: task queue #1790
Conversation
node.js/queue.md
Outdated
| - `storeLastError` (default `true`): Specifies if error information of the last failed emit should be stored in the tasks table. | ||
| - `parallel` (default `true`): Specifies if messages are sent in parallel (faster but the order isn't guaranteed). | ||
| - `timeout` (default `"1h"`): The time after which a message with `status = "processing"` can be processed again. Only for `legacyLocking = false`. | ||
| - `legacyLocking` (default `true`): If set to `false`, database locks are only used to set the status of the message to `processing` to prevent long-kept database locks. This is recommended but incompatible for parallel usage with `@sap/cds^8` instances. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is recommended? The default or setting it to false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setting it to false. however, can only be done if all task runners do so (prerequisite: they all must be on cds9)
|
my review: #1878 |
Co-authored-by: Dr. David A. Kunz <david.kunz@sap.com>
|
@renejeglinsky @smahati ready from our side |
Only for cds 9