You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce a GetIgniteInfo gRPC API endpoint to allow applications to query information about the running Ignite instance. This would enable apps to check the Ignite version (and other metadata), improving compatibility across different versions.
Motivation
Currently, there’s no standardized way for an app to determine which version of Ignite is executing it. This can lead to compatibility issues, especially when:
A new version of Ignite introduces a command that conflicts with an existing app command.
An app is built assuming specific behavior or features available only in certain Ignite versions.
By exposing version and capability information via a GetIgniteInfo API, apps can dynamically adapt or fail gracefully when incompatible versions are detected.
Use Case Example
App A is created with a custom command on Ignite v1.2.
Ignite v1.3 introduces a native command with the same name, causing a conflict.
Using GetIgniteInfo, App A can detect the version and warn the user or change behavior accordingly.
Description
Introduce a
GetIgniteInfo
gRPC API endpoint to allow applications to query information about the running Ignite instance. This would enable apps to check the Ignite version (and other metadata), improving compatibility across different versions.Motivation
Currently, there’s no standardized way for an app to determine which version of Ignite is executing it. This can lead to compatibility issues, especially when:
By exposing version and capability information via a
GetIgniteInfo
API, apps can dynamically adapt or fail gracefully when incompatible versions are detected.Use Case Example
GetIgniteInfo
, App A can detect the version and warn the user or change behavior accordingly.Proposed Response Structure
The text was updated successfully, but these errors were encountered: