Project

General

Profile

Task #2222

Story #2067: Refactor the index task generator and processor to improve scalability and performance

indexerapi generating slightly incorrect data_url

Added by Skye Roseboom about 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Skye Roseboom
Category:
d1_indexer
Start date:
2012-01-12
Due date:
% Done:

100%

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

Description

It looks like most of the generated data_url string is correct but the end of the url string seems to be missing '/' and maybe some other path info.

example for pid tao.2.1:

https://demo1.test.dataone.org:443/knb/d1/mntao.2.1

while cn resolve gives:
https://demo1.test.dataone.org:443/knb/d1/mn/v1/object/tao.2.1

Looks like a base_url value somewhere is off.

History

#1 Updated by Skye Roseboom about 12 years ago

Probably needs to make use of resolve mechanism. The old hard-coded node registry contained REST end-points as part of node map.

For example:

Switching to nodeRegistryService just returns the base URL not including the "/v1/object/" section

#2 Updated by Skye Roseboom about 12 years ago

  • Status changed from New to Closed

working in conjunction with #2224

#3 Updated by Skye Roseboom about 12 years ago

  • Status changed from Closed to In Progress

#4 Updated by Skye Roseboom about 12 years ago

  • Status changed from In Progress to Closed

adding path to the object display endpoint (/v1/object/) to the base url retrieved using the node list registry service. This issue was a side effect of removing the nodeMapList from spring context file.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)