It should be possible to define default pagination parameters at the Data Virtualization API level, while still allowing bespoke pagination configurations for individual endpoints.
Currently, pagination must be configured within each workspace, which can complicate workflows and, in some cases, negatively impact processing performance. This configuration also needs to be repeated for every workspace endpoint, leading to unnecessary duplication.
A more efficient approach would be to manage pagination at the parent API level, with the following capabilities:
-
A configuration option at the API level to enable or disable pagination globally
-
A configuration option at the endpoint level to determine whether the endpoint inherits the global API pagination settings
-
A parameter to define the default pagination size (i.e., the number of results returned per page)