[Aztables] Pagination is broken when using NewListEntitiesPager on some Cross Partition Queries

[estebanreyl]

Bug Report

• import path of package in question, e.g. /sdk/data/aztables
• SDK version: v1.1.0
  • Specify the exact commit if possible: 6c75210
• output of go version : go version go1.22.0 linux/amd64

• What happened? We encountered a situation where the default runtime pager fails to get all entities in a table when doing a cross partition scan. Instead, we will end up processing 0 entities as the More function returns false incorrectly.
• What did you expect or want to happen? When running through a cross partition query, it is possible for azure storage to return an empty list and a next partition only. In this case we need to use the partition as a continuation token to keep getting entries. Apparently, this is expected behavior https://learn.microsoft.com/en-us/rest/api/storageservices/Query-Timeout-and-Pagination and we have verified this is happening on our storage account.
• How can we reproduce it? I am still working on figuring this out, but my current guess is that if enough entities with different partitions are present in a single table this becomes more likely.
• Anything we should know about your environment.
  No

P.S. from looking at the code the fix amounts to changing the More function in sdk/dara/aztablesclient.go : NewListEntitiesPager to ignore the page.NextRowKey value. I still havent tested this and will try to follow up with a PR but want to leave this documented.

[jhendrixMSFT]

Fix will be included in aztables@v1.2.0 to be released March 5th.

[estebanreyl]

Thanks for the quick fix :)

[jhendrixMSFT]

Unfortunately there was a delay in the release, it's available now.

[estebanreyl]

No worries, thanks for the update :)