fetchNext() does not return the first result

[paulsmithkc]

• Package Name: @azure/cosmos
• Package Version: 3.17.1
• Operating system: MacOS and Azure App Services
• nodejs
  • version: 14 and 16
• browser
  • name/version:
• typescript
  • version: 4.8.4
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
After investigation we found that there is as any issue with the fetchNext() method that we are using, when we only expect one database result.

Sometimes the first call to fetchNext() will return an empty array of resources with hasMoreResults = true. In order to get the first record in this situation you have to call fetchNext() multiple times until you get a result, or hasMoreResults becomes comes false.

On the other hand fetchAll() will call fetchNext() multiple times until all the results are retrieved. (There are no more results.)

So we are switching all of the findOne() and similar methods over to use fetchAll() to avoid this problem.

To Reproduce
Steps to reproduce the behavior:

1. Insert a bunch of records into a container, with different partition keys.
2. Try to query for a single document with a unique identifier that is not the id/pk of the container. (This means that the queries will be cross partition queries.)
3. Try Step 2 for all documents in the container, until one fails to be returned by the first call to fetchNext()
4. This behavior will repeatable for the document identified in Step 3

Expected behavior
The first call to fetchNext() always returns the first query result.

Actual behavior
The first call to fetchNext() does not always return the first result.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[sajeetharan]

hi @paulsmithkc This is the expected behaviour, hasMoreResults is always true by default, it gets set to false after fetchNext if there is no more continuation!

[paulsmithkc]

@sajeetharan You misunderstood the issue.

Previously the first time fetchNext returned, it would include a result. Now you have to call fetchNext() multiple times to get the first result.

[v1k1]

Reopening to investigate further.

[abkolant-MSFT]

@paulsmithkc

Previously the first time fetchNext returned, it would include a result. Now you have to call fetchNext() multiple times to get the first result.

By "Previously" you mean at an earlier time when the database had different number of entities? This is possible because the paritions might have been different. We have a gist that describes this issue here.

Could you clarify what you meant by "Previously"?

[paulsmithkc]

I think that gist accurately describes the problem.

• Is there a reason it is labelled "secret" rather than being searchable?

• Should that gist be included in the API docs, to help explain usage/expectations for fetchNext() ?

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @bkolant-MSFT, @sajeetharan, @pjohari-ms.

Issue Details

---

• Package Name: @azure/cosmos
• Package Version: 3.17.1
• Operating system: MacOS and Azure App Services
• nodejs
  • version: 14 and 16
• browser
  • name/version:
• typescript
  • version: 4.8.4
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
After investigation we found that there is as any issue with the fetchNext() method that we are using, when we only expect one database result.

Sometimes the first call to fetchNext() will return an empty array of resources with hasMoreResults = true. In order to get the first record in this situation you have to call fetchNext() multiple times until you get a result, or hasMoreResults becomes comes false.

On the other hand fetchAll() will call fetchNext() multiple times until all the results are retrieved. (There are no more results.)

So we are switching all of the findOne() and similar methods over to use fetchAll() to avoid this problem.

To Reproduce
Steps to reproduce the behavior:

1. Insert a bunch of records into a container, with different partition keys.
2. Try to query for a single document with a unique identifier that is not the id/pk of the container. (This means that the queries will be cross partition queries.)
3. Try Step 2 for all documents in the container, until one fails to be returned by the first call to fetchNext()
4. This behavior will repeatable for the document identified in Step 3

Expected behavior
The first call to fetchNext() always returns the first query result.

Actual behavior
The first call to fetchNext() does not always return the first result.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Author:	paulsmithkc
Assignees:	sajeetharan, abkolant-MSFT
Labels:	bug, customer-reported, Client, Cosmos, Service Attention
Milestone:	azure-cosmos jan release

[github-actions]

Hi @paulsmithkc, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.