Pagination metadata URL not working correctly in REST (works fine in GraphQL) - Microsoft Data API Builder (DAB) #2926
Unanswered
AkilanP1726
asked this question in
Q&A
Replies: 1 comment
-
|
Could you delete this discussion and please submit a bug? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I’m currently preparing a Proof of Concept (PoC) using Microsoft Data API Builder (DAB) and ran into an issue with pagination on two of my views.
Here’s the behavior I’m seeing:
When I test the views in Swagger UI (REST API), the pagination metadata doesn’t seem to work correctly. Specifically, the metadata endpoint URL for related views is not returned remaining records properly (for the relationship views, instead, it returns the records of first derived view).
However, when I query the same views via GraphQL, everything works as expected - the metadata endpoint URL is returned correctly for pagination.
Has anyone else encountered this issue?
Is this a known limitation or a bug with DAB’s REST implementation?
Any suggested workarounds or configuration tweaks to get pagination metadata working correctly in REST endpoints?
Environment details:
Microsoft Data API Builder version: Microsoft.DataApiBuilder 1.5.56+61c726a0fc38ab5a1d9e52cc3593bbd2a8633aec
Database type: MS SQL Server
API mode: REST (Swagger UI) and GraphQL
Any help or pointers would be appreciated!
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions