Hi All,

Any update on this? I’m stuck at pagination of results, as my child Resources are already around 100 thousand or so.

Regards,
Rishabh
> On 07-Aug-2017, at 11:49 AM, Rishabh Jain <[log in to unmask]> wrote:
> 
> Hi all,
> 
> As a part of compliance with the latest draft, "Offset" has been introduced in the Filter Criteria. Needed a few clarification on the same.
> 
> "Offset" is used to skip that many numbers of records and return the next set of child resources as per the limit defined in the filter criteria. As per my understanding, this has a linear complexity as scanning and skipping of that many records is to be done, when performing RETRIEVE operation.
> 
> If this has been introduced to bring in the pagination capabilities to fetching results, shouldn't there be a "PagingInfo" kind of property instead of "Offset"? 
> 
> If not, kindly suggest, how "Offset" can be put to use when implementing the Filter Operation on Retrieval or Discovery.
> 
> The rationale is that offset queries are inherently inefficient (the performance will always be linear in the number of rows skipped) usually (O).
> 
> Regards,
> Rishabh
> 

########################################################################

To unsubscribe from the oneM2M_TechQuestions list, click the following link:
http://list.etsi.org/scripts/wa.exe?SUBED1=oneM2M_TechQuestions&A=1