December 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-902) Restructure planning

by Steven Hawkins (JIRA)

Restructure planning -------------------- Key: TEIID-902 URL: https://jira.jboss.org/jira/browse/TEIID-902 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 All transformation queries should be cached - not just views. All cached queries should already be validated - and not revalidated with every request. Cached queries should be stored individually - not as full and separate trees as they are now, where the same view command exists can exist multiple times in cache. The choice about whether to use a materialized view or not should also be moved to planning time - not a resolver activity. We should remove the concept of non-embedded command from everything except planning logic. It's error-prone and confusing in a resolving/rewrite context. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-808) Revisit the prior issues with extending the JOPR JMX plugin and verify if the problems have been fixed

by Van Halbert (JIRA)

Revisit the prior issues with extending the JOPR JMX plugin and verify if the problems have been fixed ------------------------------------------------------------------------------------------------------ Key: TEIID-808 URL: https://jira.jboss.org/jira/browse/TEIID-808 Project: Teiid Issue Type: Sub-task Components: Jopr Plugin Reporter: Van Halbert Assignee: Ted Jones In the development of the tech preview of MetaMatrix 5.5.3 version, it was determined that the JOPR JMX plugin had issues that did not enable us to extend for our use. This needs to be revisited because this is our first choice for discovering datasources (since JOPR is already doing it). We need to perform a filtering process which requires us to be able to discover and then interrogate the properties in order to determine if this is a Teiid datasource. -- 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, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-905) block clone method is incorrect

by Steven Hawkins (JIRA)

block clone method is incorrect ------------------------------- Key: TEIID-905 URL: https://jira.jboss.org/jira/browse/TEIID-905 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 The block clone method does not perform a deep clone. -- 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, 7 months

2
2
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, 7 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, 7 months

3
9
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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-754) LOCATE() function isn't being translated correctly by Oracle Connector

by Larry O'Leary (JIRA)

LOCATE() function isn't being translated correctly by Oracle Connector ---------------------------------------------------------------------- Key: TEIID-754 URL: https://jira.jboss.org/jira/browse/TEIID-754 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0, 6.0.0, 6.2.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 6.2.0 The rewritten/translated query for the MMx LOCATE() function to Oracle's instr() function does not appear to be correct. SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26 Is being rewritten for Oracle as: SELECT instr('234567890', to_char(SmallA.IntNum), 2) FROM SmallA WHERE SmallA.IntKey = 26 In this case Oracle will return 0 for instr() because Oracle starts at position 1. The query should be: SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26 Furthermore, if I pass a negative value to LOCATE() it appears we assume position 1. If the negative value is sent to Oracle, Oracle goes from the end of the string. We should prevent this (if not already). In 5.5.1 the rewritten query is even different and may ore may not be correct. I have not checked 5.5.3/5.5.4 and/or Westport/Teiid. Here are the test cases that should cover this issue: public void testRewriteLocate() throws Exception { String input = "SELECT locate(INTNUM, 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', to_char(SmallA.IntNum), 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate2() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp') FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate3() throws Exception { String input = "SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26"; //$NON-NLS-1$ String output = "SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate4() throws Exception { String input = "SELECT locate('c', 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT 1 FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate5() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp', -5) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum, 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-882) Look into using javax.xml.xpath in the XML-Relational connectors.

by John Doyle (JIRA)

Look into using javax.xml.xpath in the XML-Relational connectors. ----------------------------------------------------------------- Key: TEIID-882 URL: https://jira.jboss.org/jira/browse/TEIID-882 Project: Teiid Issue Type: Task Components: XML Connector Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Using the javax.xml.xpath implementation might give us a more complete XPath capability (functions, etc). -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-807) Develop the new Teiid Console using JOPR for its core framework

by Van Halbert (JIRA)

Develop the new Teiid Console using JOPR for its core framework --------------------------------------------------------------- Key: TEIID-807 URL: https://jira.jboss.org/jira/browse/TEIID-807 Project: Teiid Issue Type: Feature Request Components: Console, Jopr Plugin Affects Versions: 6.3.0 Reporter: Van Halbert Assignee: Van Halbert Use the the JOPR framework to develop the new Teiid console for administrating and monitoring a Teiid resource. -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-890) AdminShell runs as if bsh.interactive=false was specified, even though interactive

by Paul Nittel (JIRA)

AdminShell runs as if bsh.interactive=false was specified, even though interactive ---------------------------------------------------------------------------------- Key: TEIID-890 URL: https://jira.jboss.org/jira/browse/TEIID-890 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 7.0 Environment: Fedora 10, JDK Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode), 7.0 M1 build Reporter: Paul Nittel Assignee: Steven Hawkins I installed and started Teiid with a query testing VDB deployed. When I entered "SELECT * FROM Smalla;", it went back to the interactive prompt without displaying any data. Executing "bsh.interactive=true;" before the SELECT corrected the problem (otherwise I had to "printResults();") In previous versions this has worked as intended. -- 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, 7 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2009