[IGNITE-19354] Java thin 3.0: Same schema version is retrieved multiple times in concurrent scenarios

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: thin client
• Labels: ignite-3
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 24/Apr/23 12:17
• Updated: 04/Sep/24 16:10
• Resolved: 17/May/23 07:05

Description

When ClientTable.getSchema is called, we send a request for the given schema version every time, even if another request for that version is active (e.g. in case of multiple concurrent TUPLE_GET requests).

Instead of caching ClientSchema, we should cache CompletableFuture<ClientSchema>, and use computeIfAbsent to guarantee only one request for the given version. Make sure to handle failures - if a cached future is failed, send a new request.

Issue Links

• is cloned by: IGNITE-19355 .NET: Thin 3.0: Same schema version is retrieved multiple times in concurrent scenarios
• is related to: IGNITE-19241 Java thin 3.0: propagate table schema updates to client on write-only operations
• links to: IGNITE-19354 Java client: Do not load same schema more than once by ptupitsyn · Pull Request #2076 · apache/ignite-3