Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

listEntities is not retrieving the data from azure storage tables - intermittently. #30837

Closed
4 tasks
vishaldupati62 opened this issue Aug 21, 2024 · 3 comments
Closed
4 tasks
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Tables

Comments

@vishaldupati62
Copy link

vishaldupati62 commented Aug 21, 2024

  • Package Name: @azure/data-tables
  • Package Version: 13.2.2
  • Operating system: Linux
  • [ x ] nodejs
    • version: 18 LTS
  • browser
    • name/version:
  • [ x ] typescript
    • version: 4.3.0
  • Is the bug related to documentation in

Describe the bug
A clear and concise description of what the bug is.

Using "listEntity" with "byPage" is omitting data thats present in azure storage tables and can be found in Azure Portal UI.
This is happening intermittently as we see some small amount of data is being read and getting processed.

Filter thats being passed to list entities method:

odata`a eq '${a}' and b eq '${b}' and Timestamp lt datetime'${processingTime}'`

There are about 2 million entities in the table.
We are using Azure Functions with runtime version 4.

To Reproduce
Steps to reproduce the behavior:
1.

Expected behavior
Nodejs SDK should retrieve the entities from azure storage table accurately while using timestamp in the query.

Screenshots

Application Code
Note: listEntity is just a wrapper in our applicate code for the actual method 'listEntities'
Screenshot 2024-08-21 at 1 01 13 PM
Screenshot 2024-08-22 at 6 41 55 PM

Image that shows data in azure tables while the same query run through nodejs SDK giving empty array or empty response.
Screenshot 2024-08-21 at 1 06 17 PM

Additional context
Add any other context about the problem here.

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Tables labels Aug 21, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @klaaslanghout.

@jeremymeng jeremymeng assigned jeremymeng and joheredi and unassigned jeremymeng Aug 21, 2024
@vishaldupati62 vishaldupati62 changed the title listEntity is not retrieving the data from azure storage tables - intermittently. listEntities is not retrieving the data from azure storage tables - intermittently. Aug 22, 2024
@gnandyala123
Copy link

@jeremymeng jeremymeng self-assigned this Aug 24, 2024
@jeremymeng
Copy link
Member

It is known that sometimes the service returns pages with an empty list of items, but with a continuation token to get the next page. Users just need to continue to fetch next page until there's no page left.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Tables
Projects
None yet
Development

No branches or pull requests

4 participants