[jira] [Commented] (WHIMSY-204) collate_minutes update check window

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WHIMSY-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609870#comment-16609870 ] 

Sebb commented on WHIMSY-204:
-----------------------------

The fix requires knowing when the check was actually made.

Or at least knowing the earliest time it could have been done.
So one possibility would be to allow for the maximum run time and subtract that from the index file time.
At present the run times are of the order of 10-20 seconds, and the script is run every hour, so downdating by a few minutes *should* be sufficient.

> collate_minutes update check window
> -----------------------------------
>
>                 Key: WHIMSY-204
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-204
>             Project: Whimsy
>          Issue Type: Bug
>            Reporter: Sebb
>            Priority: Major
>
> collate_minutes checks to see whether there are any input files that are newer than the index file.
> If not, then it skips processing the input files.
> If there are some new files, it updates the index file at the end of processing.
> Since a run can take several seconds (and will only get longer as more minutes are added), there is a window of time - between processing a file and creating the index - during which the file can be updated.  The next run will see that the index is newer than the file so will not treat it as having changed. It will only be picked up if it is changed again (or another file is changed).
> In the worst case, it could take a month for the update to be picked up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)