storage-http: pagination with next url extracted from the page?

Open
#2,828 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api, backend

Research direction

Begin by locating the storage-http pagination implementation and compare its behavior with the linked Qlik pagination example. Done means using a response's links.next.href value to retrieve subsequent records; the issue names no file or test, so identify relevant coverage before changing the behavior.

Written by the indexing model from the issue text.

Description

enhancement

Hello

Qliksaas apis use pagination without offset params. They provide the "next" url in the response page

How could I tell drill to use "links.next.href" value for retreiving further records?

https://qlik.dev/apis/pagination-sorting-filtering

{
  "data": ["list", "of", "items"],
  "links": {
    "prev": { "href": null },
    "next": { "href": "https://example.org/api/v1/items?page=<next-cursor>" },
  }
}
Dominant language
Java
Stars
2k
Forks
989
Avg merge
1d 8h
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/drill

All issues in apache/drill

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.