IGNITE-24620 .NET: Use standard LINQ exceptions in First/Single operations#7903
Merged
Conversation
Contributor
|
@rezataroosheh please update the tests, we have some failures because the message has changed: |
ptupitsyn
approved these changes
Mar 31, 2026
ptupitsyn
changed the title
Contributor
|
@rezataroosheh thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR aligns exception behavior in .NET LINQ operations (First and Single) with standard LINQ semantics.
Previously, Ignite returned custom exception messages (e.g., "ResultSet is empty") when the result count was unexpected. This change ensures that standard InvalidOperationException messages are used instead.
Replaced custom exception messages with standard LINQ messages:
https://issues.apache.org/jira/browse/IGNITE-24620