Some of these go back to May (when we started creating batch entry import jobs).
Some of them were for user jobs for imports that were draft (for testing). I've deleted these and we should try to do a better job of cleaning up our test imports in the future.
Others are because the expires_date for the user_job is null (but should be set). To investigate why there is no date here, fix in core — and then check if this covers all of them.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Manage expiration date for user jobs on status change | wikimedia/fundraising/crm | master | +6 -4 |
Related Objects
Related Objects
- Mentioned In
- T418798: Priorities: Sprint D
- Mentioned Here
- T416040: Add filters to All / My Imports reports in core
Event Timeline
Comment Actions
This would help make things easier in the future: T416040: Add filters to All / My Imports reports in core
Comment Actions
Upstream PR to set expiration date for search batch imports.
Once this is deployed, I can delete all the old batches that don't have expiration dates.
Comment Actions
Change #1244101 had a related patch set uploaded (by Lars SG; author: Lars SG):
[wikimedia/fundraising/crm@master] Manage expiration date for user jobs on status change
Comment Actions
Change #1244101 merged by Eileen:
[wikimedia/fundraising/crm@master] Manage expiration date for user jobs on status change
Comment Actions
@Jgreen This should keep our tmp table in civicrm under control in the future. I've deleted a bunch of old import jobs / tables from before this change.
Comment Actions
That's great. Also I modified the database backups to dump these tables separately, which keeps them from tripping up the main civicrm backup when they disappear mid-backup.