June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-173) ProductAdmin role can deploy a vdb but cannot create connector bindings

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-173?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-173. ------------------------------- > ProductAdmin role can deploy a vdb but cannot create connector bindings > ----------------------------------------------------------------------- > > Key: TEIID-173 > URL: https://jira.jboss.org/browse/TEIID-173 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 8.x > Reporter: Steve Jacobs > Fix For: 7.0 > > > Defect Tracker #24544: Seems like if I have authorization to deploy a VDB, I should have authorization to create connector bindings. This should be re-evaluated. -- 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-932) Misleading error message when using quotation marks: Parse error... encountered (

by Paul Nittel (JIRA)

Misleading error message when using quotation marks: Parse error... encountered ( --------------------------------------------------------------------------------- Key: TEIID-932 URL: https://jira.jboss.org/jira/browse/TEIID-932 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.0 Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid 1/19/2010 Reporter: Paul Nittel Assignee: Steven Hawkins Using AdminShell, I entered a query: select "foo" as expected;. The result I received was: // Error: Parser Error: Parse error at line 2, column 8. Encountered: ( There was no ( in the query. The error message is misleading, especially in the case where there is a left parenthesis. Correcting the quotation marks to apostrophes produces correct results. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-895) Update the SalesForce API to version 17 (winter 10).

by John Doyle (JIRA)

Update the SalesForce API to version 17 (winter 10). ---------------------------------------------------- Key: TEIID-895 URL: https://jira.jboss.org/jira/browse/TEIID-895 Project: Teiid Issue Type: Bug Components: Salesforce Connector Reporter: John Doyle Assignee: John Doyle Fix For: 7.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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-894) Query inexplicably failing Query Testing only with MySQL

by Paul Nittel (JIRA)

Query inexplicably failing Query Testing only with MySQL -------------------------------------------------------- Key: TEIID-894 URL: https://jira.jboss.org/jira/browse/TEIID-894 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Environment: Fedora 10, Teiid 7.0.0 M1 Reporter: Paul Nittel Assignee: Steven Hawkins Series 9000, #7 fails with MySql and passes with all the other sources. Original Query SELECT BQT1.SmallA.IntKey, BQT2.SmallB.FloatNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.IntKey = BQT2.SmallB.FloatNum AND BQT1.SmallA.IntKey >= 0 AND BQT2.SmallB.IntKey >= 0 ORDER BY BQT1.SmallA.IntKey; It's supposed to return 25 rows, but returns 0. Let's ignore the "ORDER BY" since it just adds to the code (and doesn't factor into the issue since it works the same with or without). If I remove the "AND BQT2.SmallB.IntKey >= 0", it works! I get 25 rows. SELECT BQT1.SmallA.IntKey, BQT2.SmallB.FloatNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.IntKey = BQT2.SmallB.FloatNum AND BQT1.SmallA.IntKey >= 0; If I switch it so the first condition is removed and the second remains, it FAILS SELECT BQT1.SmallA.IntKey, BQT2.SmallB.FloatNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.IntKey = BQT2.SmallB.FloatNum AND BQT2.SmallB.IntKey >= 0; What doesn't it like about "BQT2.SmallB >= 0" ?? I ran this query--and the one with only "BQT1.SmallA >= 0"--with OPTION DEBUG. Stuff is attached. -- 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
9
0 / 0

[JBoss JIRA] Closed: (TEIID-249) Need well-known multi-payload container

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-249?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-249. ------------------------------- > Need well-known multi-payload container > --------------------------------------- > > Key: TEIID-249 > URL: https://jira.jboss.org/browse/TEIID-249 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #21547: Currently it's up to users to build some container and extend connectors if they want to pass multiple payloads through the system. Would probably be better if we provided such a container, JDBC connectors were aware of it, and our commandPayload() functions worked with it. -- 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-904) Error executing the Procedural releational query with out a where clause

by Ramesh Reddy (JIRA)

Error executing the Procedural releational query with out a where clause ------------------------------------------------------------------------ Key: TEIID-904 URL: https://jira.jboss.org/jira/browse/TEIID-904 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 7.0 I have virtual stored procedure called "p1" which has no input parameters. When I execute this procedure either via select * from p1; or exec p1(); in both cases it fails with error Group has an access pattern which has not been met: group(s) [vm.p1]; access pattern(s) [Access Pattern: Unsatisfied [] History [[]]] Procedures with no input parameters should not be tested for Access patterns. -- 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
3
0 / 0

[JBoss JIRA] Resolved: (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 resolved TEIID-152. --------------------------------- Fix Version/s: (was: 8.x) Resolution: Won't Fix With the other improvements to capabilities there's shouldn't be a need to work this issue. > 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] Resolved: (TEIID-188) Improve resolution of parameter references used in compare criteria

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-188?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-188. --------------------------------- Fix Version/s: (was: 8.x) Resolution: Duplicate Issue Duplicate of TEIID-235 > Improve resolution of parameter references used in compare criteria > ------------------------------------------------------------------- > > Key: TEIID-188 > URL: https://jira.jboss.org/browse/TEIID-188 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.x > Reporter: Mark Drilling > Assignee: Steven Hawkins > Priority: Minor > Attachments: GregComments.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Entering this JIRA from Issue 185605 in issue tracker. Greg Haber reports problem using Penrose off the shelf application. Example query as follows > select distinct petOwnersFromMM.owner, petOwnersFromMM.name from petVirtualDB.gregtest_virtual.gregtest.pet petOwnersFromMM where lower(petOwnersFromMM.owner) = lower(?) order by petOwnersFromMM.owner > He is getting "com.metamatrix.jdbc.MMSQLException: The function 'lower(?)' has more than one possible signature." since the lower function is ambiguous. > Workaround is to use "lower(convert(?, string))" in the sql. There is a statement in the release notes for a future enhancement that we could use the type info from the other side of the compare criteria to determine what the type should be. > I will attach Gregs further comments for reference. -- 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] Resolved: (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 resolved TEIID-227. --------------------------------- Resolution: Out of Date We no longer have the concept of a remote connector. > 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] Updated: (TEIID-168) Refine caching behavior

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-168?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-168: -------------------------------- Fix Version/s: 7.1 (was: 7.0) Labels: performance cache (was: performance) Moving remaining work with relation and procedure caching to 7.1. ResultSet caching and proper buffering of cache results was handled in 7.0. > Refine caching behavior > ----------------------- > > Key: TEIID-168 > URL: https://jira.jboss.org/browse/TEIID-168 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.1 > > > Connector resultset caching should be replaced with relation and procedure caching. This would initially be backed by the buffermanager, based upon hints/costing, and be utilized by the planner rather than the resolver. It would be good if we also detected the level of determinism. > Query resultset caching should also be backed by the buffermanager. -- 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