Utility command for integrity checking #109

New issue

Open

opened 2025-08-26 07:01:44 +00:00 by mih · 0 comments

mih commented

2025-08-26 07:01:44 +00:00

(Migrated from github.com)

Consequently, there is a need for integrity checking the content of an existing collection -- reporting any invalid records.

This is needed, in particular, because the service may not be able to deliver such records through its endpoints anymore (especially in TTL format), and thereby rules out any "migration" workflows that use the API directly.

Related to #93.

The service consumes an "external" schema definition. Nothing guarantees that this schema is a constant, it could (in principle) change at any moment -- also in ways that invalidate existing records in a collection. Consequently, there is a need for integrity checking the content of an existing collection -- reporting any invalid records. This is needed, in particular, because the service may not be able to deliver such records through its endpoints anymore (especially in TTL format), and thereby rules out any "migration" workflows that use the API directly. Related to #93.