Remember, there is already a "forget" button on the output connection,
which will remove everything associated with the connection. It's meant to
be used when the output index has been reset and is empty. I'm not sure
what you'd do different functionally.
Karl
On Tue, Jun 14, 2022 at 2:04 AM
+1.
I respect for the design concept of ManifoldCF, but I think force delete options make MCF more
useful for those who use MCF as crawler. Adding force delete options doesn't change default
behaviors and it doesn't break back-compatibility.
Koji
On 2022/06/14 14:46, Ricardo Ruiz wrote:
Hi
Hi Karl
We are using ManifoldCF as a crawler more than a synchronizer. We are
thinking of contributing to ManifoldCf by including a force job delete and
force output connector delete, considering of course the things that need
to be deleted with them (BD, etc). Do you think this is possible?
We
Because ManifoldCF is not just a crawler, but a synchonizer, a job
represents and includes a list of documents that have been indexed.
Deleting the job requires deleting the documents that have been indexed
also. It's part of the basic model.
So if you tear down your target output instance and
Hi all
My team uses mcf to crawl documents and index into solr instances, but for
reasons beyond our control, sometimes the instances or collections are
deleted.
When we try to delete a job and the solr instance or collection doesn't
exist anymore, the job reaches the "End notification" status and
