References
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Specification Performance Requirements
De-Register API Performance<insert Jira Ref, Using confluence menu options +, Jira Issue/Filter>
<optional other relevant references, Jiras, Confluence pages, external links>
Assumptions<optional>
<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>
...
Issues & Decisions
# | Issue | Notes | Decision | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Do we need a analysis template? | is convention for (new) developers to guide them | Luke Gleeson and Toine Siebelink agreed we do to have consistent pages | 2 | This is an open issue | 3 | This is a very important (blocking issue)Deleting cm handle one after another. | Can be processed into batchs | ||
| 2 | Getting cm handles by id | It should be converted to fetch by list of xpath (CPS Core) | Fetch by list of xpath using temp table | |||||||
| 3 | Delete schema set operation | cascade all | Native query using temp table | |||||||
| 4 | Updating CmHandleState | Use batch operation to update states | ||||||||
| 5 | How to do performance test ? | |||||||||
| 6 | Async response ? |
<Note. use green for closed issues, yellow for important ones if needed>
...