[Cosmos][VectorSearch] Non Streaming Order By Query

[aayush3011]

Description

• This update introduces support for non-streaming OrderBy, essential for vector search capabilities. Previously, the SDK operated under the assumption that documents returned in response to ORDER BY queries were fully ordered across all continuations. However, with the newly implemented non-streaming OrderBy feature in the backend, this assumption is no longer valid. The backend communicates this change through a new field in the Query Plan, _hasNonStreamingOrderBy, which is set to true when applicable.

• In scenarios where _hasNonStreamingOrderBy is true, a new pipeline stage for non-streaming order by is established. This stage functions as a blocking pipeline stage, similar to the GROUP BY stage, and is designed to accumulate all backend responses before yielding any results.

• A new query feature by the name of NonStreamingOrderBy has also been added.

.Net PR for the same: Azure/azure-cosmos-dotnet-v3#4362

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

com.azure:azure-cosmos

[jeet1995]

Can we reuse BadRequestException?

[aayush3011]

We can, but using this exception would provide more context in the logs to folks who don't know about this new query pipeline.

[FabianMeiswinkel]

What about also using a unique sub status code? How did .Net solve this? If we use client-side substatus code it should be consistent across SDKs

[aayush3011]

I am using this exception when we are checking for the top or limit + offset constraint. .Net doesn't has this constraint so they don't throw any exception in the logic.

Python SDk is throwing a 'raise ValueError("")` which is equivalent to an IllegalArgumentException in java.
I think we should stick with this one.

[jeet1995]

This gating is because there is no concept of continuation per FeedRange for non-streaming order by query? If so, can we name this property something like MAX_ITEM_COUNT_PER_FEED_RANGE_FOR_VECTOR_SEARCH since it is not the size of the item but the count of such items being gated. Ignore if this question doesn't make sense.

[FabianMeiswinkel]

LGTM overall - only few comments that need to be addressed left.

[FabianMeiswinkel]

Suggested change

	private static final boolean DEFAULT_AZURE_COSMOS_DISABLE_NON_STREAMING_ORDER_BY = false;
	private static final boolean DEFAULT_AZURE_COSMOS_DISABLE_NON_STREAMING_ORDER_BY = true;

[FabianMeiswinkel]

Given the issue regarding 400 for Query Plan requests the default in this month's release has to be to disable non-streaming order by queries.