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
Right now, the PollingSensor caps at 10 messages per second due to the API limit for maximum messages in a transaction and the minimum polling rate of 1 Hz.
We have modified the SQS sensor locally to be a continuously running Sensor that does its own polling loop instead of a scheduled poll as we have to handle 30+ messages per second. Would this be a welcomed upstream contribution?
The text was updated successfully, but these errors were encountered:
Right now, the PollingSensor caps at 10 messages per second due to the API limit for maximum messages in a transaction and the minimum polling rate of 1 Hz.
We have modified the SQS sensor locally to be a continuously running Sensor that does its own polling loop instead of a scheduled poll as we have to handle 30+ messages per second. Would this be a welcomed upstream contribution?
The text was updated successfully, but these errors were encountered: