Project

General

Profile

Bug #3710

ORE index processing generates URLS against the solr endpoint that are too long

Added by Skye Roseboom almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Skye Roseboom
Category:
d1_indexer
Target version:
Start date:
2013-04-09
Due date:
2013-04-09
% Done:

100%

Milestone:
CCI-1.1.2
Product Version:
*
Story Points:
Sprint:

Description

Found when testing SEAD ORE documents. An ORE that referenced 108 documents causes index processor to generate a query against the solr index that is too long and not honored by the server. Results in the ORE not being able to be processed - as the logic assumes not all referenced items are in the index (and hence the ORE is not ready to process).

On cn-stage the following ORE doc has 108 references seadva-dino-25dd5808-68cf-4a14-bd95-cd4ee2e2096a.

Its associated sci-meta is: seadva-dino-cf0ca264-c663-4e94-83f5-9b05243950b1.

The ORE is not able to be indexed due to generating a bad URL.

Need to add paging to the query logic within index processing to avoid generating URL's over 8k in length.


Related issues

Related to Member Nodes - MNDeployment #3521: SEAD Member Node Operational 2013-02-15 2013-03-11

History

#1 Updated by Skye Roseboom almost 11 years ago

  • Status changed from New to In Progress

#2 Updated by Skye Roseboom almost 11 years ago

  • Status changed from In Progress to Testing

Deployed to cn-dev and cn-stage to confirm we can place ORE with over 100 docs into the index.

#3 Updated by Skye Roseboom almost 11 years ago

  • Status changed from Testing to Closed

Deployed to all three prod CN.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)