[
https://issues.apache.org/jira/browse/IGNITE-28803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-28803:
-------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> [doc] Document IGNITE_PLUGINS system view
> -----------------------------------------
>
> Key: IGNITE-28803
> URL: https://issues.apache.org/jira/browse/IGNITE-28803
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Ignite TC Bot
> Priority: Major
> Labels: ignite-2
> Fix For: 2.19
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Source issue: IGNITE-28796
> Source PR: https://github.com/apache/ignite/pull/13256
> IGNITE-28796 adds a new SQL/control-utility system view for plugin metadata:
> `IGNITE_PLUGINS` in the `SYS` schema. The implementation exposes plugin name,
> info, version, and provider class name, and the merged change set adds SQL,
> JDBC, and control-utility tests for the new view. However, the current docs
> set does not appear to document this system view on the System Views page.
> Documentation update should clarify:
> * The `SYS.IGNITE_PLUGINS` system view is available for querying plugin
> metadata.
> * The view exposes plugin `NAME`, `INFO`, `VERSION`, and `CLASS_NAME`.
> * The System Views documentation should mention how to query the view through
> SQL and the control utility.
> Relevant implementation evidence:
> * PR #13256: https://github.com/apache/ignite/pull/13256
> * `IgnitePluginProcessor` registers the new system view and exposes plugin
> metadata.
> * SQL/JDBC/control-utility tests were updated to include `IGNITE_PLUGINS`.
> * `SqlSystemViewsSelfTest.testPluginView()` verifies selecting `name`,
> `info`, `version`, and `class_name` from the view.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
