[jira] Created: (CONNECTORS-35) Need a way to reset LCF when external conditions change
Need a way to reset LCF when external conditions change --- Key: CONNECTORS-35 URL: https://issues.apache.org/jira/browse/CONNECTORS-35 Project: Lucene Connector Framework Issue Type: Improvement Components: Framework agents process, Framework core, Framework crawler agent Reporter: Karl Wright When a change is made external to LCF, such as a Solr configuration change, LCF needs some way for a user to signal that that change took place. For example, a button or link on the view output connection page might signal some undefined global change in the target of that output connection. A similar button or link on the repository connection view page might signal a corresponding change to the underlying repository. Clicking the button would do the following things: (1) It would clear the current version string for all documents that passed through that connection. This would guarantee that the documents would be reingested if and when they were processed the next time. (2) It would reset the last job time value for all jobs affected by the connection to zero. This would guarantee that all documents belonging to that job would be rechecked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CONNECTORS-35) Need a way to reset LCF when external conditions change
[ https://issues.apache.org/jira/browse/CONNECTORS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-35: - Assignee: Karl Wright Need a way to reset LCF when external conditions change --- Key: CONNECTORS-35 URL: https://issues.apache.org/jira/browse/CONNECTORS-35 Project: Lucene Connector Framework Issue Type: Improvement Components: Framework agents process, Framework core, Framework crawler agent Reporter: Karl Wright Assignee: Karl Wright When a change is made external to LCF, such as a Solr configuration change, LCF needs some way for a user to signal that that change took place. For example, a button or link on the view output connection page might signal some undefined global change in the target of that output connection. A similar button or link on the repository connection view page might signal a corresponding change to the underlying repository. Clicking the button would do the following things: (1) It would clear the current version string for all documents that passed through that connection. This would guarantee that the documents would be reingested if and when they were processed the next time. (2) It would reset the last job time value for all jobs affected by the connection to zero. This would guarantee that all documents belonging to that job would be rechecked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
