Details
-
New Feature
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
CP: sprint 82
-
Core: Platform
Description
The new function could be part of PgUtil.getStream
Proposed prototype:
streamGet(String table, Class<T> clazz, String cql, int offset, int limit, String element, RoutingContext routingContext, Map<String, String> okapiHeaders, Context vertxContext)
The responseDelegateClass is or collectionClazz is not applicable here.. This streamGet is ONLY to be used for responses with resultInfo.schema.
From routingContext, the HTTP response can be generated.
In case of an error after the first record has been sent the connection is closed prematurely. There is no other error reporting. We do not use error reporting using HTTP trailer ( https://tools.ietf.org/html/rfc7230#section-4.1.2 ).
TestRail: Results
Attachments
Issue Links
- blocks
-
MODINVSTOR-438 stream GET for /instance, /holdings and /items
-
- Closed
-
-
MODUSERS-173 GET users as a stream
-
- Closed
-
- is blocked by
-
RMB-500 PostgresClient.streamGet with total hits and error handling
-
- Closed
-
- relates to
-
MODINVSTOR-439 Create bulk download endpoint to save id UUIDs
-
- Closed
-
-
MODINVSTOR-452 Create size optimized bulk download endpoint to save id UUIDs
-
- Open
-
-
RMB-554 PgUtil.getAllIds
-
- Open
-
-
RMB-570 Change / update when to use the RoutingContext are parameter
-
- Open
-
-
RMB-572 Avoid serialization in streamGet
-
- Open
-
-
RMB-573 streamGet with optimized SQL
-
- Open
-
-
RMB-580 Unit tests in Jenkins fail which seem related to streamGet
-
- Closed
-