Page History

...

<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>

#	Assumption	Notes
1

Issues & Decisions

#

Issue

Notes

Solution

Decision

1

Deleting fragment children with grandchildren or only grand childs or list elements

org.onap.cps.spi.impl.CpsDataPersistenceServiceImpl#deleteDataNode

Remove use of "objectA.removeIf(x -> conditions);" as it's Time complexity is O(n) that went wrost as data nodes increases.
Used hashcode to remove child fragment based on it's xpath
- - ```
  @EqualsAndHashCode.Include
  private String xpath;
```

2

Deleting parent or other cases

Replace "fragmentRepository.delete(parentFragmentEntity);" by native query where object contains 1-1, 1-many and 1-1 relationship

<Note. use green for closed issues, yellow for important ones if needed>

issue from relates story

Excerpt Include

	DW:CPS-1434: VES Message to update CPS DB
	DW:CPS-1434: VES Message to update CPS DB
nopanel	true

< we do not want to dictate the remainder of an analysis it will depend on the type of user story at hand>

...