[JBoss JIRA] (TEIID-2415) Ensure thread-safety of mutable metadata
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2415:
-------------------------------------
Summary: Ensure thread-safety of mutable metadata
Key: TEIID-2415
URL: https://issues.jboss.org/browse/TEIID-2415
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
Some metadata values can be changed at runtime, such as transformations, stats, and properties. In the case of transformations and stats an exception won't occur, but the most up-to-date value may not be read by other threads. Changing the properties could cause an exception as the map changes are not concurrency safe - similar to TEIID-2342
--
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-2414) improper handling of prepared array values
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2414:
-------------------------------------
Summary: improper handling of prepared array values
Key: TEIID-2414
URL: https://issues.jboss.org/browse/TEIID-2414
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
This is a regression from TEIID-2111. Sending an array as a parameter value which is typed as object will result in resolver exception.
--
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-2413) Need admin api methods to return properties and template for a dataSource
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2413?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2413:
-------------------------------------
I can add
{code:JAVA}
/**
* Given the deployed name of the data source, this will return all the configuration properties
* used to create the datasource. If sensitive information like passwords are masked, they will NOT
* be decrypted. "driver-name" property on the returned properties defines the template name used
* to create this data source.
*/
Properties getDataSource(String deployedName) throws AdminException;
{code}
> Need admin api methods to return properties and template for a dataSource
> -------------------------------------------------------------------------
>
> Key: TEIID-2413
> URL: https://issues.jboss.org/browse/TEIID-2413
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Affects Versions: 8.2
> Reporter: Mark Drilling
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> For the designer import work, we need a way to get the properties for a DataSource via the adminApi. Also the 'template' that was used to create it.
--
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-2067) Global temporary tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2067:
---------------------------------------
Global temporary tables are handled differently depending on the vendor. Are you looking for oracle style handling where only one such global table is defined, but will have session scoped data?
Is TEIID-196 sufficient to handle the external case?
> Global temporary tables
> -----------------------
>
> Key: TEIID-2067
> URL: https://issues.jboss.org/browse/TEIID-2067
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 7.7
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
>
> Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization.
--
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-1328) API request: Programatically modify the VDB
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1328?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-1328:
---------------------------------------
TEIID-196 - CREATE FOREIGN TEMPORARY TABLE was added for 8.3. This could be adapted to a general create on a schema with the appropriate MetadataRepository update.
> API request: Programatically modify the VDB
> --------------------------------------------
>
> Key: TEIID-1328
> URL: https://issues.jboss.org/browse/TEIID-1328
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi
> Affects Versions: 7.1
> Reporter: Mark Addleman
> Priority: Minor
>
> I'd like an API to programatically modify the VDB. It would be ideal to modify the VDB using DDL through Teiid. Our primary use case is accessing a dynamic set of datasources through Teiid. When a datasource is added, we would INSERT the appropriate entries into MODEL, PROPERTIES, DATASOURCES tables. Teiid would reread the appropriate metadata from the associated 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