[jira] [Comment Edited] (CONNECTORS-1541) Documents updated in Google Drive are send with 0 byte to CMIS Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16640919#comment-16640919 ] Karl Wright edited comment on CONNECTORS-1541 at 10/7/18 12:04 AM: --- If you can't find what commit is missing, just attach the entire connector source file to this ticket and I can commit that. Or, better yet, recompute the diff based on the current code in master. was (Author: kwri...@metacarta.com): If you can't find what commit is missing, just attach the entire connector source file to this ticket and I can commit that. > 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)
[jira] [Comment Edited] (CONNECTORS-1541) Documents updated in Google Drive are send with 0 byte to CMIS Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16640895#comment-16640895 ] Douglas C. R. Paes edited comment on CONNECTORS-1541 at 10/6/18 10:56 PM: -- [~kwri...@metacarta.com] and [~piergiorgioluc...@gmail.com] I have fixed this one too. Please, take my changes from the following commit [https://github.com/douglascrp/manifoldcf/commit/dc1ce5836ab685db5276f547ef5f5f220bae4f0d] was (Author: douglascrp): [~kwri...@metacarta.com] I have fixed this one too. Please, take my changes from the following commit https://github.com/douglascrp/manifoldcf/commit/dc1ce5836ab685db5276f547ef5f5f220bae4f0d > 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)
