Skip to content

[@azure/data-tables] - [13.2.2] - TableClient listEntities byPage - undefined continuationToken #26006

Open

Description

  • Package Name: data-tables
  • Package Version: 13.2.2
  • Operating system: Windows 10
  • nodejs
    • version: 18.16.0
  • react
    • version: 18.0.23
  • browser
    • name/version:
  • typescript
    • version: 4.8.4
  • Is the bug related to documentation in

PR: https://github.com/Azure/azure-sdk-for-js/pull/18179/files
Main: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/tables/data-tables/samples/v13/typescript/src/usingContinuationToken.ts

Describe the bug
When following the example in the PR/sample linked above, the continuation token is undefined, even though there are more records in the table.

To Reproduce
Steps to reproduce the behavior:

  const tableClient = new TableClient('The URL', 'The Table', credential)
  const iterator = tableClient.listEntities<BatchesTableRow>().byPage()

  let interestingPage: string | undefined
  for await(const page of iterator){
    console.log(page)
    for await (const value of page.values()){
      records.push(value)
    }
    interestingPage = page.continuationToken
  }

  const page = await tableClient.listEntities().byPage({continuationToken: interestingPage}).next()

  if(!page.done){
    console.log(page.value[0])

    for(const entity of page.value){
      records.push(entity)
    }
  }

The console.logs shows that the first records in both calls are the same.
The credential is an InteractiveBrowserCredential

Expected behavior
The above code should load the next 1000 records.

Screenshots
image

Additional context
I am trying to accomplish being able to get more than 1000 records from a table. The table currently has around 1800 records.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Tablescustomer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions