gnodet-bot commented on code in PR #29184:
URL: https://github.com/apache/camel/pull/29184#discussion_r4477936149
##########
components/camel-google/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc:
##########
@@ -65,5 +65,12 @@ include::partial$component-endpoint-headers.adoc[]
// component options: END
+The consumer polls a calendar and sends each event as a message, with its id
in the `CamelGoogleCalendarEventId` header.
+With `syncFlow=false` and `considerLastUpdate=true`, each poll reads all
result pages. In this mode,
+`maxResults` controls the API page size rather than the total number of events
delivered by a poll.
+This lets the consumer move past a page containing only events already seen at
the last update timestamp.
+With `considerLastUpdate=false`, non-sync polling continues to read only one
page per poll.
+
+With `considerLastUpdate`, each poll starts from the last update of the events
it has already seen:
Review Comment:
⚠️ **Truncated sentence** — this line ends with a colon but no continuation.
The main branch (PR #29161) has a YAML usage example after this sentence that
was not carried into the backport:
```suggestion
With `considerLastUpdate`, each poll starts from the last update of the
events it has already seen:
[source,yaml]
----
- route:
from:
uri: google-calendar-stream:events
parameters:
calendarId: primary
considerLastUpdate: true
clientId: "{{google.clientId}}"
clientSecret: "{{google.clientSecret}}"
refreshToken: "{{google.refreshToken}}"
applicationName: camel-example
steps:
- log:
message: "Event ${header.CamelGoogleCalendarEventId}:
${body.summary}"
----
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
