Create a Google calendar example

[oscerd]

[cunningt]

@oscerd Can I take this one?

[oscerd]

Sure

[jmerljak]

Any progress on this or #695?

[oscerd]

695 has been done here https://github.com/apache/camel-kafka-connector-examples/tree/master/google-calendar-stream/google-calendar-stream-source

[jmerljak]

I see. Perhaps a note should be added to the closed issue.

Anyway, is the example correct? I find the following line suspicious: camel.source.path.index=ckc
Shouldn't index be set to something like events/list?

[oscerd]

Yes, it's correct, otherwise I wouldn't commit it. Index is just a logical name. Anyway it has been tested

[oscerd]

Index in calendar-stream is just a logical name. Events/list would be in the plain google calendar case

[jmerljak]

Index in calendar-stream is just a logical name. Events/list would be in the plain google calendar case

Is there any documentation explaining the difference between 'plain' and 'stream' source connectors/components?

[oscerd]

In the components list of camel you can find more informations about the fields and examples. The behavior is the same between component and connector. I'll add some more information if i have time.

[jmerljak]

I'm still confused. From the documentation it is not clear to me how stream connector differs from 'plain' one, or stream component from 'plain' component respectively.

Plain one has parameters apiName and methodName. There are no such parameters on stream connector. I assumed index is corresponding parameter because the documentation states:

The Google Calendar endpoint is configured using URI syntax:
google-calendar:apiName/methodName

and

The Google Calendar Stream endpoint is an API based component and has additional parameters based on which API name and API method is used. The API name and API method is located in the endpoint URI as the null path parameters:
google-calendar-stream:index

If index is just a logical name, how are API name and method configured?

[oscerd]

The two components are completely different. With stream component you can only consume events from a calendar like a stream. So you'll receive a set of events on each poll. With the calendar component you can also produce events and that component has been based on the API component from camel.

The documentation seems to be wrong anyway.

[oscerd]

The documentation should be fixed upstream.

[oscerd]

https://camel.apache.org/components/latest/google-calendar-stream-component.html

[jmerljak]

The two components are completely different. With stream component you can only consume events from a calendar like a stream. So you'll receive a set of events on each poll. With the calendar component you can also produce events and that component has been based on the API component from camel.

Thank you, things are a bit clearer now. :)