Changes between Version 201 and Version 202 of ippToPsps

Timestamp:

Mar 9, 2012, 2:46:06 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -291 +291 @@
 
 There is a second 'hidden' argument to {{{dvoToMySQL}}}, namely {{{reset}}}. This is dangerous, as this option will reset all the tables necessary to import a DVO database. If you have spent days importing a DVO database, then run {{{dvoToMySQL}}} using this option, everything wilol be lost. The user is prompted to ask whether they really want to proceed.
-
-== Deletion policy ==
-
-When loading, three copies of the data exist: the original files on disk, the batches on the datastore and a third copy on the PSPS loading machine. The deletion policy at present is:
-
- * when a batch has been loaded to the ODM and has a status of 'merge worthy' '''or''' 'failed', then the copy on the datastore and the DXLayer's copy can be removed
- * when a batch has been successfully merged into the PSPS database, then final copy on local disk may be deleted
-
-The logic for this is that errors may occur during the merge phase and it is useful to have local copies of offending batches for debugging purposes. This standard behavior can be changed by setting the appropriate values in the ''deletion'' section of the config.
-
-To actually perform the clean, run the {{{cleanup.py}}} program like this:
-
-{{{
-./run.sh cleanup.py  configs/lap20110809.xml
-}}}
-