Would be nice to have a simple solution for ephemeral jobs that don't need to be stored in the database after completion.
The retention mechanism works well, however, it is global. For important jobs, we want to keep it high. But we also have some jobs that we don't care for after they're completed (mostly cron jobs). And if the inverval is high (e.g. once a minute), the database quickly becomes overloaded with not-very-useful data.
We thought about an option of calling JobDelete manually but it would be much more convenient to have a built-in mechanism.
Would be nice to have a simple solution for ephemeral jobs that don't need to be stored in the database after completion.
The retention mechanism works well, however, it is global. For important jobs, we want to keep it high. But we also have some jobs that we don't care for after they're completed (mostly cron jobs). And if the inverval is high (e.g. once a minute), the database quickly becomes overloaded with not-very-useful data.
We thought about an option of calling
JobDelete
manually but it would be much more convenient to have a built-in mechanism.