CDA-117: Catalog endpoint ADR#1837
Conversation
|
Should address the new QUERY HTTP method. Wouldn't be implemented in the short term, but design should take it into consideration. |
| * - Catalog endpoint HTTP method type | ||
| - Catalog endpoints currently support `GET all` requests. Support for `QUERY` requests shall be implemented for | ||
| improved functionality. | ||
| - Introduced in `RFC 10008`, the `QUERY` HTTP method allows for significantly more complex queries without |
There was a problem hiding this comment.
This should reference a GitHub issue tracking this addition given it will not be implemented until proper support is available in library versions computable with deployment targets (unless they are back porting Javalin/Tomcat? I haven't looked at it myself)
| * - Paging | ||
| - Catalog endpoints shall support paging. | ||
| - Efficient retrieval for larger data sets. | ||
| * - GetAll vs Catalog |
There was a problem hiding this comment.
I'm struggling a bit with this definition as the current catalog data types already contain enough data for a POST even though we didn't implement them. For example the location endpoint getAll and the catalog/locations and the time series identifier getAll and catalog/timeseries endpoints.
I think it would be useful for discussion if examples were presented.
QUERY is now supported in Jakarta EE 12 and implemented in Tomcat, looks like several others have gone through and done the same. |
3 participants
Summary
ADR for catalog endpoint improvements.
Related Issue
Closes #1717
Validation
Documentation only.
Checklist