OMRS REST API nextPageURL

[lpalashevski]

Description

Scope changed to remove unused functionality #6220

--
Issues discovered while testing with paged results:

1. nextPageURL returned by OMRS REST API paged responses is invalid due to missing "/" while constructing the URL.
2. pageSize parameter embedded in the nextPageURL is always 0
3. Embedded search body should be either URL encoded or (more preferred) we move from body to URL query parameters (suggest triage on the next community call)

Example (as-is):

POST {{base-url}}/servers/{{server-id}}/open-metadata/repository-services/users/{{user-id}}/instances/entity/02f79bdb-3a6c-4824-a672-f9285a62b995/relationships

{
    "class": "TypeLimitedFindRequest",
    "pageSize": 2,
    "offset": 0
}

{
    "class": "RelationshipListResponse",
    "relatedHTTPCode": 200,
    "nextPageURL": "https://localhost:9443admin/instances/entity/02f79bdb-3a6c-4824-a672-f9285a62b995/relationships{{\"class\":\"TypeLimitedFindRequest\",\"offset\":2,\"pageSize\":0}}",
    "offset": 0,
    "pageSize": 2,
    "relationships": [ ... ]
}

Fixes # (issue)
No related issue opened.

How Has This Been Tested?

Local graph repository retrieving paged relationships for entity.