Change Details

At least the metadata indexer should be, because currently, it is based on a journal client dedicated to creating one-shot tasks. This would: - simplify the stack by removing moving parts (scheduler, storage access db for content indexer...). - allow better monitoring (as we already have dashboard for journal client) Additionally, it would be an opportunity to make sure indexation is always retried on error (currently, it isn't; and failing to index one object causes the whole batch to be lost).

At least the metadata indexer should be, because currently, it is based on a journal client dedicated to creating one-shot tasks. This would: - simplify the stack by removing moving parts (scheduler, storage access db for content indexer...). - allow better monitoring (as we already have a grafana dashboard for journal clients) Additionally, it would be an opportunity to make sure indexation is always retried on error (currently, it isn't; and failing to index one object causes the whole batch to be lost).

At least the metadata indexer should be, because currently, it is based on a journal client dedicated to creating one-shot tasks. This would: - simplify the stack by removing moving parts (scheduler, storage access db for content indexer...). - allow better monitoring (as we already have a grafana dashboard for journal clients) Additionally, it would be an opportunity to make sure indexation is always retried on error (currently, it isn't; and failing to index one object causes the whole batch to be lost).