[jira] [Updated] (CAMEL-15961) Calendar Stream component: implement proper synchonization

["Andrea Cosentino (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-15961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Cosentino updated CAMEL-15961:
-------------------------------------
    Fix Version/s: 3.8.0

> Calendar Stream component: implement proper synchonization
> ----------------------------------------------------------
>
>                 Key: CAMEL-15961
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15961
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-google-calendar
>            Reporter: Jakob Merljak
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 3.8.0
>
>
> Calendar Stream component supports kind of an incremental polling by setting considerLastUpdate=true. However, this is problematic as even current events might have been updated a long time ago (e.g. recurring events) and setting {{updatedMin}} request parameter to such a value causes HTTP 410 error with message: _"The requested minimum modification time lies too far in the past."_
> A proper synchronization logic should be implemented instead. Documentation: [https://developers.google.com/calendar/v3/sync]
> Note that `syncToken` is incompatible with `orderBy`, `query`, `dateMin`, `updatedMin` and some other parameters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)