June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-152) New SQL directive OPTION NOJOINPUSHDOWN that tells query planner to not push down any joins

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-152?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-152. ------------------------------- > New SQL directive OPTION NOJOINPUSHDOWN that tells query planner to not push down any joins > ------------------------------------------------------------------------------------------- > > Key: TEIID-152 > URL: https://jira.jboss.org/browse/TEIID-152 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.x > Reporter: Greg Haber > Priority: Minor > > This capability has been requested by a customer(see I-T ticket 217562). They want us to add in the following functionality: > -add an OPTION directive (OPTION NOJOINPUSHDOWN) to MetaMatrix SQL that tells the query planner whether or not to attempt to push down joins for a particular query. This would be a general purpose MetaMatrix SQL change. The default would be for our query planner to act as it does today (do join pushdown as allowed by connector capabilities), and the behavior if this OPTION directive was used would be to instead not do any join pushdown for any part of the user query, even if allowed by connector capabilities. > What this would allow them to do, if JBEDSP-348 is also implemented, is to leverage the limited join capability that SFDC has via its "relationship query" functionality. Because SFDC doesn't have full join capabilities, this would allow them to first try to submit a query against a VDB that uses SFDC as a source and see if the part of the join that the query planner pushes down to SFDC is something that SFDC can actually do. If not, the SFDC connector would throw an error, and the customer would resubmit their query with this OPTION NOJOINPUSHDOWN option. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1038) SF connector fails to connect.

by John Doyle (JIRA)

SF connector fails to connect. ------------------------------ Key: TEIID-1038 URL: https://jira.jboss.org/jira/browse/TEIID-1038 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Changes for JCA including the migration to cxf have some residual 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

14 years, 6 months

2
3
0 / 0

[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

14 years, 6 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1128) Invalid Resolver Error

by Ted Jones (JIRA)

Invalid Resolver Error ----------------------- Key: TEIID-1128 URL: https://jira.jboss.org/browse/TEIID-1128 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Ted Jones Assignee: Steve Hawkins Fix For: 7.0 Getting the following exception executing a stored procedure with a parameter from a web service model: 11:28:24,508 WARN [PROCESSOR] Processing exception 'Error Code:ERR.015.008.0019 Message:Error Code:ERR.015.008.0019 Message:Unable to resolve element: Books_MySql_Output_View.AUTHORS_OutputView.AUTHORS_Output.AUTHORS_Output_Instance.AUTHOR_ID' for request 5A806b3/JTrd.1. Exception type org.teiid.api.exception.query.QueryPlannerException thrown from org.teiid.query.resolver.util.ResolverVisitor.handleUnresolvedElement(ResolverVisitor.java:116). The element path is valid though and should be resolved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
6
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

14 years, 6 months

6
6
0 / 0

[JBoss JIRA] Created: (TEIID-1109) NPE Connecting to a Teiid DataSource (XA) Without Setting Expected Properties

by Ted Jones (JIRA)

NPE Connecting to a Teiid DataSource (XA) Without Setting Expected Properties ------------------------------------------------------------------------------ Key: TEIID-1109 URL: https://jira.jboss.org/browse/TEIID-1109 Project: Teiid Issue Type: Bug Components: JDBC Driver Reporter: Ted Jones Assignee: Steve Hawkins Fix For: 7.0 I created a datasource for a VDB with XA sources underlying. I didn't add any of the required custom properties (server, host, etc) just used the default properties provided by the datasource template. This resulted in the following when I tried to connect: Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:394) at java.util.Properties.setProperty(Properties.java:143) at org.teiid.jdbc.BaseDataSource.buildProperties(BaseDataSource.java:194) at org.teiid.jdbc.TeiidDataSource.buildProperties(TeiidDataSource.java:106) at org.teiid.jdbc.TeiidDataSource.buildEmbeddedProperties(TeiidDataSource.java:228) at org.teiid.jdbc.TeiidDataSource.getConnection(TeiidDataSource.java:215) at org.teiid.jdbc.BaseDataSource$1.createConnection(BaseDataSource.java:340) at org.teiid.jdbc.XAConnectionImpl.getMMConnection(XAConnectionImpl.java:110) at org.teiid.jdbc.XAConnectionImpl.getConnection(XAConnectionImpl.java:96) at org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.<init>(XAManagedConnection.java:56) at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.newXAManagedConnection(XAManagedConnectionFactory.java:475) at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:453) ... 32 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
4
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

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Closed: (TEIID-227) Support remote transactional connectors

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-227?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-227. ------------------------------- > Support remote transactional connectors > --------------------------------------- > > Key: TEIID-227 > URL: https://jira.jboss.org/browse/TEIID-227 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 8.x > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The transaction changes for 5.5.2 and beyond removed the ability to perform transactions involving remote connectors. It would be best if remote participation in XA were represented through XAResources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-977) ENHANCEMENT: Sending Oracle specific commands to the data source.

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-977?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-977. ------------------------------- > ENHANCEMENT: Sending Oracle specific commands to the data source. > ----------------------------------------------------------------- > > Key: TEIID-977 > URL: https://jira.jboss.org/browse/TEIID-977 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Priority: Optional > > ENHANCEMENT: Sending Oracle-specific commands to the data source. The customer wants to send Oracle-specific commands to the data source through MMx. > Example: ALTER SESSION SET DB_FILE_MULTIBLOCK_READ_COUNT = 128. > This setting ensures that Oracle reads data extent-by-extent, which is faster, rather than block-by-block, which is slower. This is on a per session basis. > Tested successfully in Squirrel but unsuccessful using QueryBuilder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010