Hi Mikhail, Thanks for kicking off the discussion on this valuable initiative! I have left some comments on the page. I would also appreciate seeing more examples of what multithreaded code looks like using the proposed API.
Regards, Maksim On Wed, Feb 11, 2026 at 3:13 PM Dmitry Pavlov <[email protected]> wrote: > > ++1 > > a couple of questions: > - Is it possible or planned to update to modern Java futures and related APIs (our minimum version is 11, and we expect to move to 17 soon) to automatically propagate the Context, or should developers handle them manually? > - How will the static analysis rules be implemented to prevent the use of multithreading APIs that don’t automatically propagate the Context, and how will exceptions or exclusions (e.g., for thin client code) be handled? > > > > On 2026/02/05 20:16:41 Mikhail Petrov wrote: > > Igniters, > > > > Please have a look at a proposal - IEP-143 Unified Operation Context Propagation [1]. > > > > IEP-143 describes a way to implement a more robust method for attaching > > arbitrary internal data (context) to an operation and ensuring that it > > can be accessed throughout the operation's execution. > > > > Jira Ticket - [2] > > Implementation of the first step - [3] > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-143+Unified+Operation+Context+Propagation > > [2]https://issues.apache.org/jira/browse/IGNITE-26608 > > [3]https://github.com/apache/ignite/pull/12429 > >
