Content Comparison

Table of Contents

Jira Legacy

server	ONAP System Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a4733707d-557c2057-3c0c3a0f-b515ae5e-579789cceedb4fd8aff50176
key	CPS-1016

Assumptions/Decisions

...

#	Layer	Proposed Changes
1	REST Layer	openapi.yaml change /v1/data/ch/searches to /v1/ch/id-searches ncmp.yaml change queryCmHandles method to executeCmHandleIdSearch Use the CmHandleQueryRestParameters schema to both of them components.yaml merge Conditions schema to CmHandleQueryRestParameters schema delete Conditions schema
2	Controller Layer	NetworkCmProxyController Update controller methods to use the new schema Both component method call separated service method Rename queryCmHandles method to executeCmHandleIdSearch
3	Service Layer	NetworkCmProxyDataService Create new method for query cmHandles Keep queryCmHandles method and rename it to queryCmHandleIds Both method should be called separate methods in CpsAdminService Validation logic should be moved to an separated method and call it from both method CpsAdminService Update queryCmHandles method return type to Set<CmHandles> Use separate methods to CmHandlesId search (queryCmHandleIds) CpsAdminPersistenceService Update queryCmHandles method return type to Set<CmHandles> Use separate methods to CmHandlesId search (queryCmHandleIds)
4	Persistence Layer	ModuleReferenceQuery Update queryCmHandles method return type to Set<CmHandles> Update queryCmHandles method to handle both filtering parameters Create to separete method for CmHandlesId searches with new filtering parameters (use the original queryCmHandles method code)

...