[KAFKA-306] Ensure `poll.await.time.ms`only is used if there are no results. Created: 06/Apr/22 Updated: 28/Oct/23 Resolved: 10/Jan/23 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | Source |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ross Lawley | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | size-xsmall | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Quarter: | FY23Q4 | ||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Clarify the description of how it is used to block and mention the poll.interval.ms configuration which is the time between poll calls. Simplify the logic by using poll.await.time.ms via ChangeStreamIterable.maxAwaitTime instead of in the MongoSourceTask.poll(). |
| Comments |
| Comment by Githook User [ 10/Jan/23 ] |
|
Author: {'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}Message: Align change stream cursor and batching with poll batching (#127) Use `poll.await.time.ms` as the `maxAwaitTime` for the cursor
|