This message was deleted.

Hi @Yogesh Singh, Select query has been deprecated in favor of Scan queries. Pagination on scan queries can be done using

limit

and

offset

parameters. It does not have the

"fromnext":"true"

functionality that existed in the Select query type though.

I use very older version of druid and it does not support scan and we are backfilling data using select API call . Observation , we use while loop for select query with pagination specs + limit and exit from loop once we get empty result set but this approach is failing for one of the corner case with multiple partitions for a time interval and endless loop is running because don't get empty result set .

@Yogesh Singh In a previous thread you mentioned the installation you have is running 0.9.1. Is that correct? I ask because there looks to be enhancements to the select query with pagination based on a breakage in 0.9.1.x related to this bug...more information is here There is a comment in the thread that offers a workaround that may help.

The work around is to take the pagingIdentifiers returned by Druid and strip them down to only the last (latest) segment. That is returned to the web app, which includes it in the request for the next page just like the current implementation. But when the service receives that request, it parses out the starting time of the segment and uses that as the start date on the interval for the query.

Let me know if that helps.

Thanks @Tish Johnson. I can relate , this is a similar case as per above shared . i use druid version": "0.9.1.1" Seems this bug is not fixed in 0.9.1.1 version . Also tried to strip down to only the latest segment in my code but it does not work . threshold distribute the offset with multiple segments and it can be sum of multiple segments but offset length is not fix while distributing.