[
https://issues.apache.org/jira/browse/CONNECTORS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569300#comment-17569300
]
Karl Wright commented on CONNECTORS-1541:
-----------------------------------------
This looks good now. Will pull it in shortly. Thanks!!!
> Documents updated in Google Drive are send with 0 byte to CMIS Output
> Connector
> -------------------------------------------------------------------------------
>
> Key: CONNECTORS-1541
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1541
> Project: ManifoldCF
> Issue Type: Bug
> Components: CMIS Output Connector
> Affects Versions: ManifoldCF 2.10
> Reporter: Douglas C. R. Paes
> Assignee: Karl Wright
> Priority: Major
> Fix For: ManifoldCF 2.12
>
> Attachments: CmisOutputConnector.java
>
>
> When dealing with migration process, like when using the CMIS Output
> Connector to ingest content into an ECM (Alfresco in my case), I noticed that
> when a document is updated inside Google Drive, the engine is able to detect
> the change and put it into the queue to be updated into the output.
> By using the CMIS Output Connector, the document is versioned into Alfresco,
> but this new version is always created as a 0 byte file.
>
> I configured the issue as a *Framework core* because I am still not sure who
> is causing the problem, if the *GoogleDrive Connector* or the *CMIS Output
> Connector*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
