You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2022/05/23 16:14:00 UTC
[jira] [Created] (IGNITE-17022) Implement interceptors for Ignite Services
Maxim Muzafarov created IGNITE-17022:
----------------------------------------
Summary: Implement interceptors for Ignite Services
Key: IGNITE-17022
URL: https://issues.apache.org/jira/browse/IGNITE-17022
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Fix For: 2.14
Currenlty, Ignite Services has a lack of support execution a custom middleware process before and after a service execution. This leads to a lot of boilerplate code.
The IEP-79 describes a draft API of such a feature implementation:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334119
However, we still need to consider additional crucial points of such API:
- sync or async listeners/interceptors execution (some of processes may require to set and clear threadlocals);
- an exception in the inteceptrod should or should not interrupt a service execution;
- {{context}} may need to be accessible inside interceptors and services;
Also we need to add description about what kind of the {{guarantees}} are provided by Ignite server node during a service execution. It may be necessary to consider the service-per-thread execution logic.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)