Bug #3710
ORE index processing generates URLS against the solr endpoint that are too long
100%
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
History
#1 Updated by Skye Roseboom over 11 years ago
- Status changed from New to In Progress
#2 Updated by Skye Roseboom over 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 over 11 years ago
- Status changed from Testing to Closed
Deployed to all three prod CN.