Versions Compared

Old Version 13

changes.mady.by.user Niamh Core

Saved on

compared with

New Version 14

changes.mady.by.user Niamh Core

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-644


Open Issues


IssueDecision
1Should the response be a string or described using a schema?yes, we will describe the request and response using a schema
2

What approach is best for getting the data from the DB?

  1. Have two methods that execute a native query and determine intersection on ncmp side
    1. get cm handles for the given module names and revisions 
    2. get cm handles for the given module name
  2. Have one method that combines the above queries into one
  3. Iterate over the list of modules and get the cm handle id for each.

I propose to use option 1 to improve performance and readability.

3Is revision necessary for this use case?No, we agreed moduleName is only needed for now.

API details

DescriptionURISample Request BodySample Response Body
Get all cm handles that support  all modules in a given list of modules

POST {ncmpRoot}/ncmp/v1/ch/searches

 {
  "conditions": [
    {
      "name": "hasAllModules",
      "conditionParameters": [
        {
          "moduleName": "module1"

        },

        {
          "moduleName": "module2"

        }

      ]
    }
  ]
}

{
  "cmHandles": [
    {
      "cmHandleId": "cmhandle1"
    },

    {
      "cmHandleId": "cmhandle2"
    }
  ]
}

...