Bug #8542
resource Map not indexed when the resourceMap SID is used in triples.
100%
Description
This is because there is a check that all referenced ids are indexed. There is a flaw in the routine that checks in that the resourceMap SID is never found because it is never in the Hazelcast map, nor has it been indexed yet.
Other referenced objects get away with it because they are found in the index or not by SID as expected.
See IndexTaskProcessor.areAllReferencedDocsIndexed
The solution may have to be to pass in the systemMetadata, or the pid of the resourceMap so it can be looked up via Hz sysmeta map.
Related issues
Associated revisions
fixes #8542: removes the seriesID of the resourceMap from the areAllReferencedDocsIndexed check.
fixes #8542: removes the seriesID of the resourceMap from the areAllReferencedDocsIndexed check.
History
#1 Updated by Rob Nahf over 6 years ago
- % Done changed from 0 to 30
- Status changed from New to In Progress
fixed in the 2.3 branch.
#2 Updated by Rob Nahf over 6 years ago
- % Done changed from 30 to 100
- Status changed from In Progress to Closed
Applied in changeset d1|r19199.
#3 Updated by Rob Nahf about 6 years ago
- Related to Story #8702: Indexing Refactor Strategy added
