Is your enhancement request related to a problem? Please describe.
New sync from repo algorithm in 4.2.x makes use of audit table to track processed commit IDs.
This adds to the audit table size and also makes it difficult to remove older records.
Describe the solution you'd like
Consider adding a different table to keep track of the processed commits. This can be implemented in such a way that rows are automatically deleted when no longer needed (i.e.: all previous commits have been processed)
Latest version
Duplicates
Is your enhancement request related to a problem? Please describe.
New sync from repo algorithm in 4.2.x makes use of audit table to track processed commit IDs. This adds to the audit table size and also makes it difficult to remove older records.
Describe the solution you'd like
Consider adding a different table to keep track of the processed commits. This can be implemented in such a way that rows are automatically deleted when no longer needed (i.e.: all previous commits have been processed)