[IGNITE-12387] .NET Thin Client: Handle unsupported features on older server nodes gracefully

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: platforms
• Labels: .NET
• Flags: Important
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 21/Nov/19 14:49
• Updated: 19/Dec/19 19:18
• Resolved: 18/Dec/19 15:37

Description

Right now we don't check server version before doing requests for newer features like Affinity Awareness and Cluster API. This causes exceptions like "Invalid re
quest op code: 5000", which are cryptic for the user.

Fix this:

• Affinity Awareness: disable it automatically if there is no server support; log a warning to the log (add logging by adding IgniteClientConfiguration.Logger property)
• Individual methods and features like Cluster API - throw an exception with user-friendly explanation

Issue Links

• is related to: IGNITE-12471 .NET Thin Client: WithExpiryPolicy crashes client connection on old servers
• relates to: IGNITE-12415 .NET: Thin client does not connect to old server nodes
• links to: GitHub Pull Request #7149