Support listing and exporting of recorded segments
Add new APIs in the Search and Recording specification to be able to list and export recorded segments towards a cloud storage.
Updated the proposal based on feedback received since the F2F. Added "paging" mechanism to both the search and export operations.
@jflevesque-genetec @HansBusch I re-reviewed this PR and #541 is there much more to do on this PR for 25.06 release.
There is just a need for another approval correct?
Accidentally directly pushed latest update instead of creating a PR. Removal of StoragePath aligned with Jose, but editorial change to improve readability needs review.
Note that I didn't remove the statement, unless the OmitSequenceNumber is set to True.. As the parameter isn't defined in schema and the path alogrithm bnf require the counter either the sentence has to be removed or the specs updated.
@jflevesque-genetec @HansBusch During prototyping I realized that specification is not saying anything about the span length. We can assume that span size is defined by number of export jobs for specified time range or use span duration from recording configuration. Whatever will be decided it should be mentioned in the specification to avoid confusion.
If we're talking about span duration, and not segment duration, the only visible effect would be the _end file and the segment counter. For those, we left it a bit vague on purpose, to allow a device to use directly its recorded data if it already records locally with the right format, and already allocated span counter in file names. But to also allow a device that converts on the fly from it underlying storage, to reset the span counter as it wishes.
We're willing to add a clarification if needed, but I'm just not sure what it should be in this case.
@jflevesque-genetec noticed you lads have not updated the Revision list on this.