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

Karl Wright commented on CONNECTORS-827:
----------------------------------------

I verified that, while the button cleans out the ingeststatus table, the code 
actually sends the delete request to the connection despite there being no 
ingeststatus row.  This was designed originally to save time, but clearly in a 
case of a lost connection it is problematic.

There may also be an "end notification" that takes place at the end of the job 
termination which, if it takes place, would happen no matter what.  I'll have 
to confirm that.

If there is no job notification, in my view the fix is simply to check whether 
there is an ingeststatus row before going ahead with the delete request.

> Unable to delete the jobs once a Solr core associated with the output 
> connector gets removed or is inaccessible
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-827
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-827
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Solr-4.x-component
>    Affects Versions: ManifoldCF 1.1.1, ManifoldCF 1.2, ManifoldCF 1.3, 
> ManifoldCF 1.4.1
>         Environment: Windows, JDK 1.7, HSQLDB
>            Reporter: Swami Rajamohan
>              Labels: Jobs, SolrOutputConnector
>
> If for some reason the Solr Output Connector loses the Solr core it is 
> associated with (either because the core was deleted or the connection to the 
> core was not available), there is no way to currently delete jobs associated 
> with that Connector. 
> The only kludge way to get around this, is to manually clear out the 
> INGESTSTATUS for entries corresponding to the Output Connection Name.
> Ideally it would be nice to have a mechanism to force delete the jobs even if 
> the Solr Output Connector is unable to reach its Solr Core.
> While the intent of the current behavior is to probably make sure that all 
> content associated with the core is removed on deletion of the job. There is 
> always a use case where the Solr Core itself might contain items only from 
> the job and if there is no Solr Core, there is no reason to attempt to delete 
> content from the index.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to