Can delete-all also remove the job?

5 views
Skip to first unread message

Kick Megatron

unread,
Dec 10, 2013, 2:52:03 AM12/10/13
to megatron...@googlegroups.com
HI, thanks for the beta version yesterday. Runs like a charm and solved my problems. Reduced 76K lines to ~1500 unique IP addresses with a max of 2 lines kept per IP.


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?


Ps. One side note - when using the DiffProcessor - a delete-all is not removing that history. That is required to be done manually in you tmp/diff-processor-old-files/ directory (no problem - just a note for others).

Thanks,
Kick

Tor Johnson

unread,
Dec 10, 2013, 5:01:30 AM12/10/13
to megatron...@googlegroups.com, Kick Megatron
> 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

Kick Megatron

unread,
Dec 13, 2013, 8:19:32 AM12/13/13
to Tor Johnson, megatron...@googlegroups.com
Hi Tor, late response but thanks for the feedback.
Enough ways to work around it, but agree that —delete-all suggests removal of the file from the DB.

Ps. The occurrence filter really works as a charm and saved my week.

Thanks,
Kick
> --
> You received this message because you are subscribed to the Google Groups "Megatron Hacking" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to megatron-hacki...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

Reply all
Reply to author
Forward
0 new messages