...
| Issue/Question | Decision | Notes |
|---|---|---|
| What is the proposed approach to be used in CPS? Do we use the approach as per postgREST where the REST queries are executed directly as database queries without the need of any ORM? | As per an exchange on Slack, we are not going with the postgREST model. And instead stick to using the cps-ri layer as it is? https://onapproject.slack.com/archives/C03UJAZAV3K/p1711714427478109 | |
| The proposal says the query search parameter will look something like this, ?select=name, price.gt.100. But in the postgREST documentation we can see that things entities like name and price are considered columns in a data base while in this proposal these are mentioned as leaf data node. I don't think ?select=name, price.gt.100 will be possible and instead we need to work with the jsonb objects and use arrow operators,- >, as mentioned in postGREST. But then again, the use of arrow operator is possible when we are directly executing queries at database level.If we are going to use the cps-ri layer as it is then what approach needs to be implemented to search for a particular leaf node under a data node? Need to finalize this. | ||
| postgREST implements operators that are translated to SQL queries, for example "eq" translated to =. How do we implement these operators in our approach? | ||
| How to handle parsing of requests. And multiple search requests. | ||
| Need to define Structure of data being returned, just returning a leaf can be confusing as leaves with same name can exist under different data nodes | ||
| Need grammar to handle the search equation and different kinds of data types in the querysearch, for instance Strings, Arrays and Integers in a query. These can be sent individually in a request or maybe combined in same request as well. |
...