Relational: Implement split query for non-include collections

[smitpatel]

Resolves #21234
Resolves #22283
Resolves #23803

[ghost]

Hello @smitpatel!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[ghost]

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

1. Azure Pipelines

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this

From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.

[NatanBagrov]

Hello,
Still regarding issue #23803, you said it is resolved - but when I remove the configuration (back to default warning settings) I still get warnings.

So should I put "dummy" OrderBy statements? Anything else?

[smitpatel]

@NatanBagrov - please file a new issue with code which reproduces what you are seeing. In #23803 bug report, you explicitly said that false warning happens only when split query is turned on and not otherwise. Since the old path hasn't changed, I am not sure why are you getting warnings if you remove split query configuration.