Actions
Bug #14959
closed
Batch Store Run Agent can be limited only in days for catching up old report
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Priority:
65
Name check:
Fix check:
Regression:
Description
The store run agent batch, that identify all agent runs, catches up old reports, but the limit is in days
On large install, it can be problematic - we may have millions of reports in a day, so handling them all in one go may crash the system
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by François ARMAND about 5 years ago
- Description updated (diff)
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Infrequent - complex configurations | third party integrations
- Effort required set to Very Small
- Priority changed from 0 to 65
I don't how to keep compatibility but still allows people to specify less than day.
Perhaps we could try to parse the string as a float (but well, "0.1" day is not that friendly).
Or perhaps just default to days if unit not specified (ie if Integer.parseInt() works) else try to parse as a duration.
Updated by Nicolas CHARLES about 5 years ago
- Related to Bug #15062: Allow only catching up with recent runs in agent report processing batch added
Actions