[
https://issues.jboss.org/browse/TEIID-5619?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5619:
---------------------------------------
Possible changes:
||priority||description||
|high|requests|
|high|sessions|
|high|transactions|
|med|query plan table - there's an existing issue on allowing show plan to work with
pg|
|med|virtualdatabase properties and other information (connection type, security domain,
imported schema?) exposed.|
|low|cache stats/types|
|low|worker/engine stats|
Procedures:
* Many of the existing procedures only make sense with features in WildFly, such as
connection type, changing the role mappings, update/add/remove sources, mark datasource
available, etc. I would not add sysadmin procedures for those at this point.
* restartVDB - there is a case to be made for a properly permissioned user to restart a
vdb without restarting a pod, but likely the way to do this is just to restart the vm.
* terminate session/transaction/request would be good to have
An initial cut would be to add tables/procedures for transactions, sessions, and
requests.
Provide tables representing admin information
---------------------------------------------
Key: TEIID-5619
URL:
https://issues.jboss.org/browse/TEIID-5619
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
Information provided over the admin api about sessions, requests, transactions, etc.
should also be available via system tables.
Similarly many of the admin operations could be provided as system procedures - kill
session, flush cache, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)