[ 
https://issues.apache.org/jira/browse/CONNECTORS-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-567.
------------------------------------

    Resolution: Won't Fix

We can revisit this someday; seems though like a rare edge case.

> Extended seeding interface which provides document versions
> -----------------------------------------------------------
>
>                 Key: CONNECTORS-567
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-567
>             Project: ManifoldCF
>          Issue Type: Wish
>            Reporter: Maciej Lizewski
>
> There are some cases when seeding function can provide document version with 
> data it already has.
> Current data flow needs one call to addSeedDocuments, then call to 
> getDocumentVersions, which essentialy must fetch same data, and after that 
> one more call to processDocuments. The last one probably needs separate call 
> because it needs to fetch document body, however seeding and getting versions 
> in many cases work on very same data (and probably duplicating requests to 
> repository).
> Now - reducing number of needed request to repository by eliminating 
> getDocumentVersions call for document which have version returned by 
> addSeedDocuments could significantly reduce load.
> getDocumentVersions would still be called for older docuemnts (not returned 
> by addSeedDocuments) to check if they were modified or deleted.
> This is only proposition...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to