Change Details

Depending upon which vendor product is chosen (particularly a "daily" feed option), there will be a need to implement the following functionality for the API to MySQL/MariaDB ETL: # A mechanism to chunk a data insert/update over a period of time (see: T305114#7824528 and related comments) # A mechanism to properly invalidate historical data after a given time period (e.g. data over X time units old should be flushed from the db) # Define and implement any fallback mechanisms if API or database becomes unavailable.

Depending upon which vendor product is chosen (particularly a "daily" feed option), there will be a need to implement the following functionality for the API to MySQL/MariaDB ETL: # A mechanism to chunk a data insert/update over a period of time (see: T305114#7824528 and related comments) # A mechanism to properly invalidate historical data after a given time period (e.g. data over X time units old should be flushed from the db) {T325642} # Define and implement any fallback mechanisms if API or database becomes unavailable.

Depending upon which vendor product is chosen (particularly a "daily" feed option), there will be a need to implement the following functionality for the API to MySQL/MariaDB ETL: # A mechanism to chunk a data insert/update over a period of time (see: T305114#7824528 and related comments) # A mechanism to properly invalidate historical data after a given time period (e.g. data over X time units old should be flushed from the db) {T325642} # Define and implement any fallback mechanisms if API or database becomes unavailable.