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
Is your feature request related to a problem? Please describe.
At present the maximum back-off delay (for SQS, not sure if others) is hard coded, we would like to be able to set that to a user defined value
Describe the solution you'd like
A configuration option to set the maximum back-off delay
Describe alternatives you've considered (Optional)
Hi everyone,
I just got across a talk on open search by @dlvenable and was really inspired to make a contribution.
So I would like to make small contribution on this issue.
My approach will be as follows:
Update S3SourceConfig Class:
Add a new field for MAXIMUM_DELAY.
Provide a getter method for the new field.
Modify SqsService Class:
Remove the hard-coded MAXIMUM_DELAY.
Use the new configuration parameter s3SourceConfig.getMaximumBackoffDelay() to set the maximum back-off delay dynamically.
Update Configuration File:
Add a new parameter maximum_backoff_delay to the configuration file to allow users to specify the maximum back-off delay.
This will make the maximum back-off delay user-configurable, enhancing the flexibility and usability of the SqsService class.
Is your feature request related to a problem? Please describe.
At present the maximum back-off delay (for SQS, not sure if others) is hard coded, we would like to be able to set that to a user defined value
Describe the solution you'd like
A configuration option to set the maximum back-off delay
Describe alternatives you've considered (Optional)
Additional context
Sourced from #3726
The text was updated successfully, but these errors were encountered: