Changes between Version 4 and Version 5 of Ticket #1870


Ignore:
Timestamp:
Nov 9, 2018, 1:16:04 PM (6 years ago)
Author:
Dimitar Misev
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1870

    • Property Owner changed from bphmahuu to ahambasan
    • Property Status new → assigned

  • Ticket #1870 – Description

    v4 v5  
    11In the case of a growing archive of data (where new data is continuously being added), it would be convenient to automatically ingest this data in rasdaman as soon as it becomes available.
    22
    3 One idea to support this is through an option in the ingredients file. This is pretty natural as the ingredients file fully specifies how the coverage is constructed. E.g.
     3The idea is to support this through an option for wcst_import.sh:
    44{{{
    5 "watch": True,
    6 or
    7 "watch": <interval in seconds>
     5--watch [interval (seconds)]
    86}}}
     7By default interval=3600 if none is specified.
    98
    10 With such an option in the ingredients:
    11 1. User executes `wcst_import.sh`
    12 2. wcst_import.sh ingests the currently available data as collected by the "paths"
    13 3. Rather than exiting at the end, it continues running as a daemon (#1896) that regularly checks for new data. When new data becomes available, the ingestion is automatically done with the same ingredients file to update the coverage.
    14 
    15 '''Note:''' while not a hard dependency, it would be nice to implement #1896 along with this ticket.
     9When `--watch` is specified:
     101. `interval` is as specified, or 3600 (1 hour) otherwise
     111. `--daemon` is implied
     121. The daemon runs the ingestion as usual and waits for it to finish
     131.'''After''' the first execution of wcst_import.py finished, daemon waits for `interval` seconds, then runs wcst_import.py again, and so on in a cycle