manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1541) Documents updated in Google Drive are send with 0 byte to CMIS Output Connector
Date Sat, 06 Oct 2018 23:42:00 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640918#comment-16640918
] 

Karl Wright commented on CONNECTORS-1541:
-----------------------------------------

[~douglascrp] Patch didn't apply.
Did you miss a commit?



> 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: Piergiorgio Lucidi
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message