[JBoss JIRA] (TEIID-2404) Expose buffermanager monitoring properties
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2404:
-------------------------------------
Summary: Expose buffermanager monitoring properties
Key: TEIID-2404
URL: https://issues.jboss.org/browse/TEIID-2404
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.3
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
We should expose:
BufferServiceImpl.getUserBufferSpace - the number of megs currently used by the buffermanager disk storage.
A rough total of the memory buffer space used can be added, which would be from the BufferFrontedCacheStore concurrent bits set X block size.
Also the BufferManagerImpl could report the total estimate of objects held in memory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2403) SAML support in Teiid based web services
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2403:
-----------------------------------
Summary: SAML support in Teiid based web services
Key: TEIID-2403
URL: https://issues.jboss.org/browse/TEIID-2403
Project: Teiid
Issue Type: Feature Request
Components: Server, SOAP Services
Reporter: Ramesh Reddy
Currently there is no built in support for SAML based authentication for OData based REST Services and also REST based WAR created automatically. They should provide an option to support SAML.
Designer based web services (REST, SOAP) are not part of this JIRA, they should be handled using a separate TEIIDDES JIRA.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2401) Add explicit state locks to processor and connector work
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2401:
-------------------------------------
Summary: Add explicit state locks to processor and connector work
Key: TEIID-2401
URL: https://issues.jboss.org/browse/TEIID-2401
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
Over successive refactorings there is no longer a single read barrier for multiple threads that process the work items. If needed the connector lock can be exposed to translators.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2400) Expose all JDBC Datasource creation properties through Admin API
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2400?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2400.
---------------------------------
Labels: CR1 (was: )
Resolution: Done
Exposed all the properties that AS7 reports back on CLI call
/subsystem=datasources/data-source=blah:read-resource-description
through "getTemplateProperties" call. Only excluded some properties that are used to supply custom classes to configure certain advanced functionality.
Also added "connection-properties" property to the list, when this property is supplied in the form
key1=value1,key2=value2
through "createDatasource" method, they will be supplied to jdbc driver in creation of the connection. This is a generic mechanism to provide any property to the jdbc connection that is driver specific. All other properties are defined by the AS7.
> Expose all JDBC Datasource creation properties through Admin API
> ----------------------------------------------------------------
>
> Key: TEIID-2400
> URL: https://issues.jboss.org/browse/TEIID-2400
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: CR1
> Fix For: 8.3
>
>
> Currently only certain predefined properties for the JDBC data source are exposed through Admin API. Thus if user is creating a datasource through Designer they do not have access to all the properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-196) Support creation of temp tables on physical sources.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ]
Steven Hawkins commented on TEIID-196:
--------------------------------------
Satisfied the first item above by requiring a CREATE permission on the targeted schema. This may require a designer change if they don't allow the user to select schema level permissions.
> Support creation of temp tables on physical sources.
> ----------------------------------------------------
>
> Key: TEIID-196
> URL: https://issues.jboss.org/browse/TEIID-196
> Project: Teiid
> Issue Type: Feature Request
> Components: Connector API, Query Engine
> Affects Versions: 6.0.0
> Reporter: Ken Johnson
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> This is a multi-part request.
> First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables.
> Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among:
> -- memory/cache
> -- a source represented by a connector binding
> -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance)
> Ideally default selectoin should be override-able at temp table creation time through a DDL extension
> In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months