April 2010 - teiid-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (TEIID-1033) Add state to request metadata

by Steven Hawkins (JIRA)

Add state to request metadata ----------------------------- Key: TEIID-1033 URL: https://jira.jboss.org/jira/browse/TEIID-1033 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 We should add state to request metadata to differentiate between queries that are long running and those that have simply been left open by the client. Possible values: PROCESSING DONE (result set is complete, but the Statement is still open) CANCELED We could also add a new state to differentiate between requests that have been created and queued, but not yet processed. -- 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-864) Need new deployment packing that works with JBoss AS or JBoss Embedded

by Ramesh Reddy (JIRA)

Need new deployment packing that works with JBoss AS or JBoss Embedded ---------------------------------------------------------------------- Key: TEIID-864 URL: https://jira.jboss.org/jira/browse/TEIID-864 Project: Teiid Issue Type: Sub-task Components: Build/Kits Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 Once all Connectors are in RAR format, and engine in RAR format the old deployment needs to be removed and new deployment needs to be defined, where a user can use in combination with JBoss based containers. Basically, this process needs to combine all the resources in similar directory structure with JBoss Tools, where a user can download JBoss AS or JBoss Embeeded and overlay the Teiid deployment on top of it and start using it. To begin with Teiid will only support JBoss Container, however it should be easy enough to support any JCA container, as all the components are written to JCA API. If community is interested they can use either Jenks or Glassfish containers, however the configuration needs to be developed for those containers. -- 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-859) Connector API must extend the JCA 1.5 API

by Ramesh Reddy (JIRA)

Connector API must extend the JCA 1.5 API ----------------------------------------- Key: TEIID-859 URL: https://jira.jboss.org/jira/browse/TEIID-859 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 The connector API must be modified such that it extends the JCA API http://java.sun.com/j2ee/connector/ This will enable Teiid Connectors be used as JEE Connectors in a JEE container. By the end it will pass as "JCA" connector with Teiid specific extensions (Current API). The Connector API base classes should provide skeleton adaptors for the JCA API. -- 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-941) MOD function in Postgres push down is producing connector error

by Warren Gibson (JIRA)

MOD function in Postgres push down is producing connector error --------------------------------------------------------------- Key: TEIID-941 URL: https://jira.jboss.org/jira/browse/TEIID-941 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins MOD function in Postgres push down is producing error on connector. Example: SELECT DoubleNum, 11, MOD(DoubleNum, 11) FROM BQT1.SmallA ORDER BY DoubleNum Error Code:0 Message:Error Code:0 Message:Error occurred on connector PostgreSQL_Push<14> - Error Code:0 Message:ERROR: function mod(double precision, numeric) does not exist Executing statement: [SQL: SELECT g_0."doublenum" AS c_0, 11 AS c_1, MOD(g_0."doublenum", 11.0) AS c_2 FROM "smalla" AS g_0 ORDER BY c_0] -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-883) Convert model/group/element to schema/table/column

by Steven Hawkins (JIRA)

Convert model/group/element to schema/table/column -------------------------------------------------- Key: TEIID-883 URL: https://jira.jboss.org/jira/browse/TEIID-883 Project: Teiid Issue Type: Sub-task Components: Documentation Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 The non-standard terms model/group/element should be changed to schema/table/column. This affects our runtime metadata object names, system tables, documentation, and error messages. The model to schema change represents a bit of a mismatch between the designer view of the world and Teiid. Designer models are allowed to contain catalog and schemas, but at runtime they simply become part of the table name. -- 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-1003) Connector api language changes

by Steven Hawkins (JIRA)

Connector api language changes ------------------------------ Key: TEIID-1003 URL: https://jira.jboss.org/jira/browse/TEIID-1003 Project: Teiid Issue Type: Feature Request Components: Connector API Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 With the JCA work we are in a position to make several cleanups to the connector api. First the metadata interfaces (Element, Group, etc.) are no longer necessary - as all of our metadata will be supplied via VDBs. Previously preview mode execution still supplied metadata via the QueryMetadataInterface, which then required the wrapper metadata objects. The proposed change here is to just allow for direct use of the metadata record objects. These objects are already part of the api, since they are needed for dynamic vdb work. This would address TEIID-851. Second, and more far reaching, I would like to get rid of the I(Something) interfaces fronting the connector language impl objects. The are several reasons for this: -inconsistent I prefix usage -it no longer forces the protection of the impl objects, since they have been moved into the connector api as well (this change simplifies the dependencies between a connector and the engine). -it's an oppurtunity to use more standard names for the sql constructs. -moves another step closer to consolidating the engine and connector language implementations. To that last point here is a proposal for name changes: IAggregate - AggregateFunction IBaseInCriteria - BaseInCondition IBatchedUpdates - BatchedUpdates ICommand - Command (Statement may be a better alternative) ICompareCriteria - Comparison ICompoundCriteria - AndOr ICriteria - Condition IDelete - Delete IElement - ColumnReference IExistsCriteria - Exists IExpression - Expression IFrom - From IFromItem - TableReference IFunction - Function IGroup - NamedTable IGroupBy - GroupBy IInCriteria - In IInlineView - DerivedTable IInsert - Insert IInsertExpressionValueSource - ExpressionValueSource IInsertValueSource - InsertValueSource IIsNullCriteria - IsNull IJoin - Join (JoinedTable may also be good, since it is consistent with the other TableReference classes) ILanguageObject - LanguageObject ILikeCriteria - Like ILimit - Limit ILiteral - Literal ILogicalCriteria - removed, can already be inferred if a condition is not a Predicate IMetadataReference - MetadataReference INotCriteria - Not IOrderBy - OrderBy IOrderByItem - SortSpecification IParameter - Argument IPredicateCriteria - Predicate IProcedure - Call *I would also like to update the parser and string form of exec to use the call keyword, since it is standard IQuery - QuerySpecification IQueryCommand - QueryExpression IScalarSubquery - ScalarSubquery ISearchedCaseExpression - SearchedCase ISelect - Select ISelectSymbol - DerivedColumn ISetClause - SetClause ISetClauseList - SetClauseList ISetQuery - SetQuery ISubqueryCompareCriteria - SubqueryComparison ISubqueryContainer - SubqueryContainer ISubqueryInCriteria - SubqueryIn IUpdate - Update -- 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
4
0 / 0

[JBoss JIRA] Created: (TEIID-1080) Change Admin API, to support the Translation Layer and Connection layer concepts.

by Ramesh Reddy (JIRA)

Change Admin API, to support the Translation Layer and Connection layer concepts. --------------------------------------------------------------------------------- Key: TEIID-1080 URL: https://jira.jboss.org/jira/browse/TEIID-1080 Project: Teiid Issue Type: Sub-task Components: AdminApi Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Now that we have two separate layers to define a connector the Admin API must be modified to aid in managing the lifecycle of the Translation Layer and Connection Layer. Some obvious methods will be - addTranslator(name, properties) - deleteTranslator(name) will keep the current data source methods for the connection. The previous names with "Connection Factory" will be removed/renamed. -- 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
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2010