Hi all, +1 overall.
I believe we need to more precisely specify which public API changes require an IEP (for example, adding metrics, modifying log messages, etc.) so that the rules are unambiguous for everyone. Aleksandr's questions about log messages and internode messages are a good illustration of why this clarification matters. On Tue, Oct 6, 2026 at 3:37 PM Aleksandr Chesnokov <[email protected]> wrote: > Hi all, > > > Adding to Kirill's questions: do we have a clear definition of "Public > APIs or their supported behavior"? To be more specific: > > 1. Are log messages part of the public API? As far as I know, some users > build grep scripts on top of Ignite logs. > > 2. Are internode messages part of the public API? Should we create an IEP > for a change of the wire protocol (the order of fields in a message, for > example)? > > As an example, Hadoop has an explicit compatibility guide [1] which > declares audience (who may rely on it) and stability (how freely it may > change) for each kind of interface. The two are separate: log output is > "Public and Unstable" [2], server-server wire protocols are "Private and > Stable" by default [3]. Maybe we can add a similar list to the proposal? > > > [1] > https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Compatibility.html > [2] > https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Compatibility.html#Log_Output > [3] > https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Compatibility.html#Wire_Protocols
