[IGNITE-18510] Sql. CompositePublisher is not thread safe

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: sql
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Iurii Gerzhedovich
• Reporter: Iurii Gerzhedovich
• Created: 09/Jan/23 09:16
• Updated: 17/Jan/23 12:19
• Resolved: 17/Jan/23 10:00

Description

Currently our CompositePublisher is not threadsafe, but we have to deal with 3 types of potentially concurrent signals when arbitrating Flow.Subscriptions:

1. A request(long) call from downstream that has to be routed to the current Flow.Subscription
2. A cancel() call from downstream that has to be routed to the current Flow.Subscription and cancel any future Flow.Subscription.
3. A setSubscription(Flow.Subscription) that is called by the current Flow.Subscriber after subscribing to any Flow.Publisher which is not guaranteed to happen on the same thread subscribe() is called

Let's reimplement our CompositePublisher

Issue Links

• Blocked: IGNITE-18227 Sql. Support RO transaction by index scan
• links to: GitHub PR #1511
• links to: GitHub Pull Request #1511