[
https://issues.jboss.org/browse/TEIID-5619?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5619:
---------------------------------------
Adding requests and transactions are straight-forward. Adding sessions is trickier given
the relationship between dqpcore and the sessionservice. The current design effectively
makes the session service the primary object and has the dqp injected there (due to the
legacy of supporting many session services). Usages of both together is done only by
higher level constructs (at the EmbeddedServer and TeiidAdd level). There is a hack to
set the session service on the buffermanager, so for now I'll leverage something like
that, but then circle back to make the session service a dependent object of the core.
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)