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

Takumi Yoshida commented on CONNECTORS-916:
-------------------------------------------

Hi Karl,

I sort out my understandings. is this right?

addOrReplaceDocument()
- the connector keep all documents data on local disk.
- if there are documents having id as same as documents on local disk, the 
connector overwrite them. 

notifyOfJobComplete() 
- the connector build chunks of documents from local disk and send chunk to 
Amazon one by one.
- if Amazon callback success for a chunk, the connector delete the document 
data containing in the chunk from local disk.
- if Amazon callback fail(s) for a chunk, the connector keep "all" document 
data containing in the chunk on local disk. at the next cycle of job, these 
documents are resent by connector.

> Amazon CloudSearch output connector
> -----------------------------------
>
>                 Key: CONNECTORS-916
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-916
>             Project: ManifoldCF
>          Issue Type: New Feature
>          Components: Amazon CloudSearch output connector
>    Affects Versions: ManifoldCF 1.7
>            Reporter: Takumi Yoshida
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.7
>
>         Attachments: 0507.diff, 0520.diff, 0520_2.diff, 1.patch, 2.diff, 
> 3.diff, AmazonCloudSearchParam.java, AmazonCloudSearchSpecs.java, 
> exception_handling.diff, exception_handling_2.diff, licenselist.txt
>
>
> I wrote some codes snipetts of output connector for Amazon CloudSearch.
> I would like you to review my code. You can crawl web site and feed HTML page 
> to Amazon CloudSearch.
> but it is not perfectly completed followoing reason.
> - does not write any codes for configuration page.
> - supporting file type is only HTML
> Thank you for your time,
>  Takumi Yoshida



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

Reply via email to