Project

General

Profile

Bug #8542

resource Map not indexed when the resourceMap SID is used in triples.

Added by Rob Nahf almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_indexer
Target version:
-
Start date:
2018-04-14
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

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

Related to Infrastructure - Story #8702: Indexing Refactor Strategy New 2018-09-24

Associated revisions

Revision 19199
Added by Rob Nahf almost 4 years ago

fixes #8542: removes the seriesID of the resourceMap from the areAllReferencedDocsIndexed check.

Revision 19199
Added by Rob Nahf almost 4 years ago

fixes #8542: removes the seriesID of the resourceMap from the areAllReferencedDocsIndexed check.

History

#1 Updated by Rob Nahf almost 4 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 almost 4 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 over 3 years ago

  • Related to Story #8702: Indexing Refactor Strategy added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)