Skip to content
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

Add Setting to Update ProjectionExecutionTimeout via gRPC Client #321

Open
CindyLoMinChung opened this issue Sep 9, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@CindyLoMinChung
Copy link

CindyLoMinChung commented Sep 9, 2024

Description: Currently, the ProjectionExecutionTimeout setting, which controls the allowed execution time for projection scripts, cannot be modified directly via the gRPC client. This setting is critical for managing projection behavior, especially in scenarios where complex projections or high-load environments require a longer timeout.

Feature Request: Add support to the gRPC client to allow updating the ProjectionExecutionTimeout for projections. This would provide developers with more control over projection configurations, enabling them to modify the timeout dynamically via client-side code, without having to do it manually for each projection from the ESDB UI projection config tab

Expected Behavior:

Users should be able to set or modify the ProjectionExecutionTimeout value for a given projection through the gRPC client API.
This setting should be adjustable per projection or globally for all projections managed via the client.
Use Case: In environments where projections require more processing time, users need the ability to set a higher timeout to prevent projections from faulting due to timeouts. Allowing this setting to be configured programmatically via the gRPC client would improve flexibility and prevent interruptions in long-running projection tasks.

Environment:
EventStoreDB Version: 23.10.1

Additional Information: This feature would be particularly beneficial in scenarios where projections need to be managed dynamically, as it allows developers to handle different environments and workloads without changing the server configuration files.

@w1am w1am self-assigned this Sep 10, 2024
@w1am w1am added the enhancement New feature or request label Sep 10, 2024
@w1am w1am removed their assignment Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants