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
{{ message }}
This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
I see in issue #13 that QueueBatch doesn't respect host.json for the maxPollingInterval setting. Does it also ignore the rest of the host.json settings for queues as well?
In particular I'm interested in setting the # of batches that can be retrieved and processed in parallel. The equivalent setting for single messages is the batchSize parameter. Also the newBatchThreshold for getting a new batch when the # processed gets down to a certain threshold. Is there an equivalent for these settings using the attribute or does QueueBatch already respect these settings from host.json?
The text was updated successfully, but these errors were encountered:
Hi there. Thank you for raising this but for it's been a while since I took a look at this repo and can't answer your question right out of my head. This reminded me that I probably should have archived it a while ago to do not set wrong expectations.
Just to not leave you hanging, when working on it I didn't do much to respect host.json or anything so highly likely this is a no.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I see in issue #13 that QueueBatch doesn't respect host.json for the maxPollingInterval setting. Does it also ignore the rest of the host.json settings for queues as well?
In particular I'm interested in setting the # of batches that can be retrieved and processed in parallel. The equivalent setting for single messages is the batchSize parameter. Also the newBatchThreshold for getting a new batch when the # processed gets down to a certain threshold. Is there an equivalent for these settings using the attribute or does QueueBatch already respect these settings from host.json?
The text was updated successfully, but these errors were encountered: