> There was one item I was hitting a couple of times while testing with a test file.
> When using —delete-all, the command is not removing the actual entry from the Job table - causing MD5 clashes with the test file.
>
> Can the delete-alll also removing the job from the DB?
Hmm, I have to think about this request for change. I may see it as a feature and not as a bug :)
You don't risk to process a log file several times if the job is not deleted. On the other
hand, the name --delete-all implies that everything related to the specified job is deleted.
I have to do some thinking.
> [...] causing MD5 clashes with the test file.
When testing, setting "general.fileAlreadyProcessedAction=rerun" in the job-type will rerun the
file without an error. This property can have the following values: error|skip|rerun
When testing a new job-type (configuration), I use "--no-db --export" to avoid that the
job is stored in the database.
/Tor