Closed shashank-boyapally closed 1 week ago
With the changes in fmatch, looks good to me. I just doubt the SingletonLogger
With the changes in fmatch, looks good to me. I just doubt the
SingletonLogger
Merging the PR for now, as this can be revisited later as an improvement.
so generally LGTM. i just have 1 question. why are we limiting it to just days/hours and not opening it up to "normal" time inputs. ie 1Y2M3h4m2s ? and/or to expand on that allowing a straight date input if you know the cutoff date and dont want to math the days/hours.
The idea was to have a lookback period, and run orion as a post step of our jobs. The lookback period will act as a sliding window. We can have cutoff date too in the next feature add. And the precision of seconds, since our jobs are atleast 1h apart, I assumed a precision of hours should work, no harm in having it upto seconds too.
Type of change
Description
You can now constrain your look-back period using the
--lookback
option. The format for look-back isXdYh
, where X represents the number of days and Y represents the number of hours. Do not merge until #43 gets merged, and fmatch 0.0.8 is releasedRelated Tickets & Documents
Checklist before requesting a review
Testing