AnsweredAssumed Answered

CMIS: Avoid events of temporary/internal objects in change log

Question asked by cdw on Mar 12, 2015
Latest reply on Aug 26, 2015 by nicolasraoul
I am playing with the current version of CmisSync (2.3) that checks now the Alfresco Change Log to see if there is something relevant to sync.
Unfortunately, when a node was deleted, Alfresco does not provide additional properties (incl. path name), so CmisSync is not able to determine whether this event was relevant or not and starts a new full crawl.
During my investigations I saw that there are not only DELETE events if someone removes or moves a file - there are also events of nodes that are created and vanish immediately (maybe temporary nodes for renditions or building the index). So, if someone browses a file or uploads one somewhere in the repository, CmisSync has to crawl everything new, as it finds a non-existing node in the changelog.

Now my question: Is it possible to configure that auditing application so that those "internal events" are hidden?

And: Is there a chance that Alfresco will add those properties to the changelog one day?

Best regards,
Daniel Winkler

Outcomes