HarvestMoreFrequently - Status on Failure/ReRun?

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Modify harvestMoreFrequent... such that search term is not valid
2.execute harvestMoreFrequent
3.

What is the expected output? What do you see instead?
I would expect search query to fail and the lastsuccessfulrun to have some 
state (even done) that allows processing to continue for other tables
I see the lastsuccessfulrun table left with a state of "Running" and then there 
does not appear to be a way to clear that table/row such that query can be 
fixed and job re-run
Is there some way to clear the status of a row lastsuccessfulrun 

What version of the product are you using? On what operating system?
1.0.0.3 - Windows

Please provide any additional information below.
I understand that Running in LastsuccessfulRun stops other harvesting from 
occurring. Makes sense. But if you have an issue/failure, I not sure how to 
clear that table or have it continue to next table short of dropping all tables 
vand re-running

Original issue reported on code.google.com by mwall...@ziaconsulting.com on 26 Sep 2014 at 11:05

[GoogleCodeExporter]

There are quite some JavaScript commands you can use to control the state of 
the reporting database. I will crete a wiki page for those soon...

reporting.setAllStatusesDoneForTable();   
^^ This call will reset all statusses to 'done' (instead of 'Running' which can 
be blocking for future harvest actions...

reporting.dropTables("document,links,forum")
^^ It expects a string, a comma separated list of table names. Each of the 
tables will be dropped. It will drop any table in the schema/database, no 
additional checks done. 

reporting.dropLastTimestampTable()
^^ drops the entire lastsuccesfullrun table. This will force harvesting to 
harvest everything it can find in the repository. New rows will be inserted 
only if it doesn't exist already in the reporting database.

reporting.clearLastTimestampTable("document")
^^ Execute against a single table name. It will make sure te lastrun date is 
erased, thus everything will be harvested.

Original comment by tjarda.p...@incentro.com on 6 Oct 2014 at 9:50

• Changed state: Fixed