indexer: Use CompositeObjId as object id type for ContentIndexer
Previously, content indexers were only using content sha1 as object identifier but this could lead to errors in production when attempting to fetch content data from an object storage where key is the sha256 checksum of the content (winery for instance). So ensure to use a CompositeObjId dictionary as content object identifier to avoid these kind of issues when indexing content objects.
Showing
- swh/indexer/fossology_license.py 7 additions, 16 deletionsswh/indexer/fossology_license.py
- swh/indexer/indexer.py 11 additions, 11 deletionsswh/indexer/indexer.py
- swh/indexer/metadata.py 14 additions, 11 deletionsswh/indexer/metadata.py
- swh/indexer/metadata_detector.py 3 additions, 3 deletionsswh/indexer/metadata_detector.py
- swh/indexer/metadata_dictionary/base.py 24 additions, 6 deletionsswh/indexer/metadata_dictionary/base.py
- swh/indexer/mimetype.py 8 additions, 7 deletionsswh/indexer/mimetype.py
- swh/indexer/tests/metadata_dictionary/test_codemeta.py 4 additions, 1 deletionswh/indexer/tests/metadata_dictionary/test_codemeta.py
- swh/indexer/tests/metadata_dictionary/test_npm.py 10 additions, 5 deletionsswh/indexer/tests/metadata_dictionary/test_npm.py
- swh/indexer/tests/metadata_dictionary/test_nuget.py 3 additions, 2 deletionsswh/indexer/tests/metadata_dictionary/test_nuget.py
- swh/indexer/tests/metadata_dictionary/test_python.py 3 additions, 2 deletionsswh/indexer/tests/metadata_dictionary/test_python.py
- swh/indexer/tests/test_fossology_license.py 5 additions, 5 deletionsswh/indexer/tests/test_fossology_license.py
- swh/indexer/tests/test_indexer.py 4 additions, 3 deletionsswh/indexer/tests/test_indexer.py
- swh/indexer/tests/test_metadata.py 2 additions, 2 deletionsswh/indexer/tests/test_metadata.py
- swh/indexer/tests/utils.py 23 additions, 12 deletionsswh/indexer/tests/utils.py
Loading
Please register or sign in to comment