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

Karl Wright commented on CONNECTORS-916:
----------------------------------------

bq. I think we need to clean up repository when a job is deleted or is called 
"reset seeding". I cloud not find method which are triggered in OutputConnector 
class.

When a job is deleted, all documents belonging to that job are removed from the 
index.  So the standard case will be handled properly already.

The only case that isn't actually handled well is if you click any of the 
special buttons (for example "reindex all documents" or "remove associated 
records") on the output connection's view page, and then delete the job.  The 
output connector is not currently called in these cases, but it should be easy 
to add support for that.  I will think about it further.


> 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