Push partition key to epk range resolution out of RequestInvokerHandler to consumers

[adityasa]

RequestInvokerHandler is changing the FeedRangePartitionKey to FeedRangeEpk, (regardless of what the upstream asked for). Apart from obvious concerns of doing this at such a low level (in a rather blind manner), there are at least 2 issues that I see here. Upstream (say query enumerators) have no knowledge of this and no control over this. Test infra (for e.g. InMemoryContainer) does not seem to mimic this behavior (so we are missing coverage).

azure-cosmos-dotnet-v3/Microsoft.Azure.Cosmos/src/Handler/RequestInvokerHandler.cs

Line 516 in 5788326

internal static async Task<FeedRange> ResolveFeedRangeBasedOnPrefixContainerAsync(

This was discussed in the SDK sync and acknowledged as something that should be addressed. This issue is logged to track this work.

[adityasa]

@kirankumarkolli - fyi. Please reassign as appropriate.

[kirankumarkolli]

@ealsur you were exploring if there are any gaps in CF (CFP, PULL) or feedrange API's any update?

[ealsur]

CFP does not use HPK, it either sends a PKRangeId or an Epk, nothing else.

For CF Pull I don't know, we would need a real account to be able to test, there is no way to test this otherwise. Looking at the source code, it uses this:

azure-cosmos-dotnet-v3/Microsoft.Azure.Cosmos/src/Pagination/CrossPartitionRangePageAsyncEnumerator.cs

Line 235 in 80647ba

private static async Task<IQueue<PartitionRangePageAsyncEnumerator<TPage, TState>>> InitializeEnumeratorsAsync(

azure-cosmos-dotnet-v3/Microsoft.Azure.Cosmos/src/Pagination/DocumentContainer.cs

Lines 49 to 53 in 80647ba

	public Task<TryCatch<List<FeedRangeEpk>>> MonadicGetFeedRangesAsync(
	ITrace trace,
	CancellationToken cancellationToken) => this.monadicDocumentContainer.MonadicGetFeedRangesAsync(
	trace,
	cancellationToken);

The output of that method is always FeedrangeEpk, so I would think it only uses FeedrangeEpk into the pipeline.

[kirankumarkolli]

Thanks @ealsur , for now lets track it for HPK tests gaps coverage.

Wondering how we can reliably test this scenario with live account?