Skip to content

[FEATURE] New setting which defines what to do with unsupported pagination requests #1765

@Yury-Fridlyand

Description

@Yury-Fridlyand

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:

  1. Return a error
  2. Process as a non-paginated request (ignore fetch_size parameter) as it is reported in [BUG] Non-paginated results returned silently if query not supported by cursor #78
  3. 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

  1. Until it is not deprecated/deactivated

  2. Legacy engine may fail processing that query, V2 cannot track this

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpaginationPagination feature, ref #656

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions