douardda zack ardumont
- Group Reviewers
- Maniphest Tasks
- T1384: Document indexer architecture / metadata pipeline
- rDCIDX55e039cad540: Explain in text what each metadata indexer does.
rDCIDX1153c57d9e9b: Document the metadata workflow.
You need to make the "assets" make target available for the main doc process to build your images.
In your sequence diagram, it looks strange that you try to retrieve existing metadata from the "Graph Storage", but you upload newly created metadata (in the alt box) only to the "Indexer Storage"
nitpick: we usually use dashes as filename separator for doc files, please favor that over the underscore here
|4 ↗||(On Diff #2379)|
We should clarify which kind of metadata we are talking about here. In the past with @moranegg we have agreed on the following terminology:
You should consider starting this document documenting this distinction.
Failing that (e.g., because we want to document the distinction properly elsewhere), you should at least stick to the terminology of intrinsic metadata in the documentation, because it's the workflow about them that you are documenting, not the other one.
Build was aborted
Link to build: https://jenkins.softwareheritage.org/job/DCIDX/job/tox/109/
See console output for more information: https://jenkins.softwareheritage.org/job/DCIDX/job/tox/109/console
Build was aborted
Link to build: https://jenkins.softwareheritage.org/job/DCIDX/job/tox/110/
See console output for more information: https://jenkins.softwareheritage.org/job/DCIDX/job/tox/110/console
pretty sure what the thanks means but hey ;)
Explicitely content_metadata_get is a call from the indexer_storage api.
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DCIDX/job/tox/239/
See console output for more information: https://jenkins.softwareheritage.org/job/DCIDX/job/tox/239/console