May 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1078) Build annotation based configuration for the Connector Translation layer

by Ramesh Reddy (JIRA)

Build annotation based configuration for the Connector Translation layer ------------------------------------------------------------------------- Key: TEIID-1078 URL: https://jira.jboss.org/jira/browse/TEIID-1078 Project: Teiid Issue Type: Sub-task Components: Connector API Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Since the Translation layer in no longer a JCA, the properties that are specific to Translation layer need to be modified into annotation based properties backed JAXB based beans. These properties need to exposed through "templates" for the Translation layer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1089) Combine the ExecutionFactory and Capabilities class into single class

by Ramesh Reddy (JIRA)

Combine the ExecutionFactory and Capabilities class into single class --------------------------------------------------------------------- Key: TEIID-1089 URL: https://jira.jboss.org/jira/browse/TEIID-1089 Project: Teiid Issue Type: Sub-task Components: Connector API Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Now that Translator development is focused around single class "ExecutionFactory", it makes sense to merge the capabilities also into this class. This simplifies the programming model for developing a "translator". Essentially, the users need to extend this single class for developing the custom connectors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1056) Required Connector Properties Should Have A Default Value If They Are Marked As An Expert Property

by Dan Florian (JIRA)

Required Connector Properties Should Have A Default Value If They Are Marked As An Expert Property -------------------------------------------------------------------------------------------------- Key: TEIID-1056 URL: https://jira.jboss.org/jira/browse/TEIID-1056 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.0 Environment: Teiid 7.0 M3, Ubuntu 9.04 Reporter: Dan Florian Assignee: Steven Hawkins Fix For: 7.0 The JDBC connector's "connection-definition" property is marked as an expert property but does not have a default value. Expert properties generally require very little maintenance and are normally not presented initially to a user. If a default value cannot be assigned to a required property it should not be marked as "expert." There might be other connectors with similar issues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

6
6
0 / 0

[JBoss JIRA] Created: (TEIID-1046) Component Name of the VDB is null through Profile Service

by Ramesh Reddy (JIRA)

Component Name of the VDB is null through Profile Service --------------------------------------------------------- Key: TEIID-1046 URL: https://jira.jboss.org/jira/browse/TEIID-1046 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 When the VDB is accessed using the profile service, the component name is null. This makes impossible to search for component by its name. With out this the search must be done using component type. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-1071) Modify validation errors element in schema for VDB configuration file to include attribute for location of error

by John Verhaeg (JIRA)

Modify validation errors element in schema for VDB configuration file to include attribute for location of error ---------------------------------------------------------------------------------------------------------------- Key: TEIID-1071 URL: https://jira.jboss.org/jira/browse/TEIID-1071 Project: Teiid Issue Type: Feature Request Affects Versions: 6.2.0 Reporter: John Verhaeg Assignee: Steven Hawkins Fix For: 7.0 The Designer needs this information to allow the user to navigate to the offending object within a model. So, we either need a specific attribute for location, or a generic properties element like within the model and entry elements -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-943) Fully implement client streaming of lobs/readers/streams

by Steven Hawkins (JIRA)

Fully implement client streaming of lobs/readers/streams -------------------------------------------------------- Key: TEIID-943 URL: https://jira.jboss.org/jira/browse/TEIID-943 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1 Client transmission of large objects is either not implemented or is implemented through fully materializing. We should instead allow for streaming backed by temp files on the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1045) Provide a admin method to "export" a Data Source.

by Ramesh Reddy (JIRA)

Provide a admin method to "export" a Data Source. ------------------------------------------------- Key: TEIID-1045 URL: https://jira.jboss.org/jira/browse/TEIID-1045 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 7.0 As of 7.0 M3, there is no admin method to export a data source that is defined inside the AS. This needs to be supported for the tooling purposes. Also, the "addDataSource" only supports to create XA data sources. It should also allow to create "local" data sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-944) Provide a separate Admin connection

by Ramesh Reddy (JIRA)

Provide a separate Admin connection ----------------------------------- Key: TEIID-944 URL: https://jira.jboss.org/jira/browse/TEIID-944 Project: Teiid Issue Type: Sub-task Components: AdminApi, Server Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Currently the Admin API can be accessed from JDBC API and as well a separate connection on the same port as the JDBC connection. Since in the container environment the Admin API is based on the Profile Service this needs to be on its own connection that is subject to the same authorization checks as of the profile service/jmx-console. It will no longer available on the JDBC connection. Although, we can still serve the both connections on same port as the JDBC, by having a separate port the traffic on the Admin connection can be by default encrypted always, and the number of IO threads will be limited and do not hog the JDBC connection threads. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-851) API improvements for custom connector development

by Mark Drilling (JIRA)

API improvements for custom connector development ------------------------------------------------- Key: TEIID-851 URL: https://jira.jboss.org/jira/browse/TEIID-851 Project: Teiid Issue Type: Feature Request Components: Connector API Affects Versions: 6.1.0 Reporter: Mark Drilling Assignee: Steven Hawkins Priority: Minor I'm building a custom connector, and I was trying to figure out a way to get information on whether or not a certain column in a Source Model is a Primary or Foreign Key. Here's an example of the code I've been trying: MetadataID mdID = group.getMetadataID(); //group is an IGroup String tableName = metadata.getObject(mdID).getNameInSource(); However, there doesn't appear to be a way to determine which column is Primary or Foreign Key. One thing I did notice playing around with the API, the MetadataObject contains a TableRecordImpl object that contains all sorts of MetaData info. That class appears to have tons of great info, along with getters and setters, including one called getForeignKeyIDs. Don't know if there's maybe a reason it's abstracted such that we can't get to it, but being able to get that and the other info out of that object could be highly beneficial. Maybe this is something that could be added to the API in the future? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1042) AdminShell - deployVDB assumes the -vdb.xml file is in the server's deploy folder

by Paul Nittel (JIRA)

AdminShell - deployVDB assumes the -vdb.xml file is in the server's deploy folder --------------------------------------------------------------------------------- Key: TEIID-1042 URL: https://jira.jboss.org/jira/browse/TEIID-1042 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 7.0 Environment: Fedora 12, Java(TM) SE Runtime Environment (build 1.6.0_17-b04), Teiid 7 M3 Reporter: Paul Nittel Assignee: Steven Hawkins I started AdminShell and attempted to deploy a VDB using: deployVDB("/home/pnittel/TeiidGoodies/sakila-vdb.xml"); I received the following exception: java.io.FileNotFoundException: /home/pnittel/Teiid7m3/jboss-5.1.0.GA/server/default/deploy/home/pnittel/TeiidGoodies/sakila-vdb.xml (No such file or directory) // Error: // Uncaught Exception: Method Invocation internalAdmin.deployVDB : at Line: 17 : in file: URL: jar:file:/home/pnittel/Teiid7m3/teiid-adminshell-7.0.0-SNAPSHOT/lib/teiid-adminshell-7.0.0-SNAPSHOT.jar!/scripts/adminapi.bsh : internalAdmin .deployVDB ( vdbFile , new FileInputStream ( new File ( vdbFile ) ) ) Called from method: deployVDB : at Line: 6 : in file: <unknown file> : deployVDB ( "/home/pnittel/TeiidGoodies/sakila-vdb.xml" ) Target exception: java.lang.reflect.UndeclaredThrowableException Nested: Class: SingleInstanceCommunicationException not found in namespace : at Line: 70 : in file: URL: jar:file:/home/pnittel/Teiid7m3/teiid-adminshell-7.0.0-SNAPSHOT/lib/teiid-adminshell-7.0.0-SNAPSHOT.jar!/scripts/util.bsh : SingleInstanceCommunicationException It appears to have erroneously appended my file location to that of the server's deploy folder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2010