-
Notifications
You must be signed in to change notification settings - Fork 190
[FEATURE] New setting which defines what to do with unsupported pagination requests #1765
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
enhancementNew feature or requestNew feature or requestpaginationPagination feature, ref #656Pagination feature, ref #656
Description
Is your feature request related to a problem?
A user can send a paginated request with a query which contains features not compatible with pagination. (for example: in memory sorting or aggregation)
What solution would you like?
A new SQL plugin configuration parameter should define how such request should be processed:
- Return a error
- Process as a non-paginated request (ignore
fetch_sizeparameter) as it is reported in [BUG] Non-paginated results returned silently if query not supported by cursor #78 - Fall back to legacy engine 12
TODO:
- Define
- Parameter name and value names
- Default value
- Error type for 1
- Implement
What alternatives have you considered?
N/A
Do you have any additional context?
Current behavior: fall back to V1 according to 3
Footnotes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestpaginationPagination feature, ref #656Pagination feature, ref #656