[JBoss JIRA] (TEIID-5710) Create remaining spring docs
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5710?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5710:
----------------------------------
Fix Version/s: 12.3
(was: 12.2)
> Create remaining spring docs
> ----------------------------
>
> Key: TEIID-5710
> URL: https://issues.jboss.org/browse/TEIID-5710
> Project: Teiid
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Presuming that the embedded, dev, and security docs will all be available as part of their respective code (javadocs and examples), that leaves admin, caching, and client-dev as the remaining books that need a spring specific spin.
> Most of the admin guide is not applicable - but we do need to capture somewhere all of the information related to system/env properties
> Most of the caching guide is TBD - but the sections on result set and other caching are still applicable.
> Most of the client guide is applicable to spring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (TEIID-5737) should let the system/env properties override the client properties
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5737:
-------------------------------------
Summary: should let the system/env properties override the client properties
Key: TEIID-5737
URL: https://issues.jboss.org/browse/TEIID-5737
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.2
As a follow-up to TEIID-5314 - it left things on the client as allowing the properties file override all. It should be that the system/env take precedence over the properties file.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (TEIID-5736) General odata function mapping
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5736:
-------------------------------------
Summary: General odata function mapping
Key: TEIID-5736
URL: https://issues.jboss.org/browse/TEIID-5736
Project: Teiid
Issue Type: Quality Risk
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.3
We are currently mapping procedures and functions defined by ddl to odata functions/actions. The latter is due that the function is represented in our system metadata as a procedure. We need to decide if all functions should be mapped. There's also the notion of a composable function that could be helpful.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (TEIID-5619) Provide tables representing admin information
by Steven Hawkins (Jira)
[ 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)
6 years, 11 months