You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When the client does not specify a page count for search the server defaults to a page size of 10 and there is no way to change it.
Describe the solution you'd like
I would like the ability to control the default page size on the server so that it is increased for each request without specifying it in each client request.
Describe alternatives you've considered
If the client wants a different page size, it can provide the _count parameter on each request. We may not always have control of the client code and it would be nice to be able to control default behavior on the server side.
Acceptance Criteria
1.
GIVEN [a configuration property exists in the server config file]
AND [the user has configured the server with a different value than the default]
WHEN [the user searches for any resource without specifying the _count parameter]
THEN [the server uses the page size configured in the server config file]
2.
GIVEN [no page size configuration is specified in the server config file]
WHEN [the user searches for any resource without specifying the _count parameter]
THEN [the server uses the default page size (10)]
3.
GIVEN [a configuration property exists in the server config file]
AND [the user has configured the server with a value larger than the maximum allowed size]
WHEN [the user searches for any resource without specifying the _count parameter]
THEN [the server logs a warning and uses the maximum allowed page size]
The text was updated successfully, but these errors were encountered:
This address LinuxForHealth#2229 by creating a configuration property
fhirServer/core/defaultPageSize that controls the number of records
retrieved by search when no _count parameter is specified in the
request. This parameter honors SearchConstants.MAX_PAGE_SIZE (1000). If
the server configuration specifies a value greater than MAX_PAGE_SIZE, a
warning is logged and MAX_PAGE_SIZE is used. When no configuration
property is specified the previous default
FHIRConstants.FHIR_PAGE_SIZE_DEFAULT (10) will be used.
Signed-off-by: Corey Sanders <corey.thecolonel@gmail.com>
Is your feature request related to a problem? Please describe.
When the client does not specify a page count for search the server defaults to a page size of 10 and there is no way to change it.
Describe the solution you'd like
I would like the ability to control the default page size on the server so that it is increased for each request without specifying it in each client request.
Describe alternatives you've considered
If the client wants a different page size, it can provide the _count parameter on each request. We may not always have control of the client code and it would be nice to be able to control default behavior on the server side.
Acceptance Criteria
1.
GIVEN [a configuration property exists in the server config file]
AND [the user has configured the server with a different value than the default]
WHEN [the user searches for any resource without specifying the _count parameter]
THEN [the server uses the page size configured in the server config file]
2.
GIVEN [no page size configuration is specified in the server config file]
WHEN [the user searches for any resource without specifying the _count parameter]
THEN [the server uses the default page size (10)]
3.
GIVEN [a configuration property exists in the server config file]
AND [the user has configured the server with a value larger than the maximum allowed size]
WHEN [the user searches for any resource without specifying the _count parameter]
THEN [the server logs a warning and uses the maximum allowed page size]
The text was updated successfully, but these errors were encountered: