[jira] [Commented] (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=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)
[jira] [Commented] (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=17569132#comment-17569132 ] Douglas C. R. Paes commented on CONNECTORS-1541: [~kwri...@metacarta.com] I have just created a new PR [https://github.com/apache/manifoldcf/pull/134] I hope this time the formatting is right. Please, let me know if it can be accepted now. > 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)
[jira] [Commented] (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=17567382#comment-17567382 ] Karl Wright commented on CONNECTORS-1541: - [~douglascrp], we cannot accept the patch as written because it changes the formatting of the entire files being touched from 2 spaces per indent to 4. This makes it impossible to see the actual diff. Can you resubmit without changing the formatting please? > 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)
[jira] [Commented] (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=16640932#comment-16640932 ] Douglas C. R. Paes commented on CONNECTORS-1541: The source code has been attached > 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 > 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 (v7.6.3#76005)
[jira] [Commented] (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 commented on CONNECTORS-1541: - 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] [Commented] (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=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)
[jira] [Commented] (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 commented on CONNECTORS-1541: [~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)
[jira] [Commented] (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=16638934#comment-16638934 ] Karl Wright commented on CONNECTORS-1541: - You can try sending the documents to the File System output connector and see if they get written. That should tell us more definitively where the issue lies. > 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] [Commented] (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=16638866#comment-16638866 ] Douglas C. R. Paes commented on CONNECTORS-1541: I will have to spend some hours on this tomorrow. > 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] [Commented] (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=16638839#comment-16638839 ] Karl Wright commented on CONNECTORS-1541: - I see that the length is 1334538. That should be what the CMIS output connector sees. So [~piergiorgioluc...@gmail.com] will need to look at this. > 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] [Commented] (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=16638725#comment-16638725 ] Douglas C. R. Paes commented on CONNECTORS-1541: This is one case https://www.dropbox.com/s/dog65xuwmfd4gn5/0%20byte%20sample%20injection.ods?dl=0 > 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: Framework core >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] [Commented] (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=16638689#comment-16638689 ] Karl Wright commented on CONNECTORS-1541: - [~douglascrp], can you look at the Simple History report for the document that has zero bytes on output, and see what it gives for a length? > 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: Framework core >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)
