July 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1586) Increase audit information

by Steven Hawkins (JIRA)

Increase audit information -------------------------- Key: TEIID-1586 URL: https://issues.jboss.org/browse/TEIID-1586 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins AuditMessages should include the Session object and the request id, so that custom logging can access additional information. login events should also capture more detail including IP (and possibly MAC), etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-1677) Exists subqueries will unnest by default

by Steven Hawkins (JIRA)

Exists subqueries will unnest by default ---------------------------------------- Key: TEIID-1677 URL: https://issues.jboss.org/browse/TEIID-1677 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Exists subqueries should respect the default unnest property, rather than always unnesting. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1639) Unable to build on a file system that isn't formatted to support case-sensitivity

by Van Halbert (JIRA)

Unable to build on a file system that isn't formatted to support case-sensitivity --------------------------------------------------------------------------------- Key: TEIID-1639 URL: https://issues.jboss.org/browse/TEIID-1639 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 7.4, 7.4.1 Reporter: Van Halbert Assignee: Van Halbert Priority: Critical Trying to build the 7.4.1 branch and trunk, but unable to due to the metadata project contains 2 vdb files; Test.vdb and test.vdb in the the src/test/resources directory. Each are for different tests. This problem is due to a filesystem hasn't been formatted to support case-sensititivity. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1632) Provide something like an ECHO statement in the procedure language that can assist a user in debugging their procedure logic

by Van Halbert (JIRA)

Provide something like an ECHO statement in the procedure language that can assist a user in debugging their procedure logic ----------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1632 URL: https://issues.jboss.org/browse/TEIID-1632 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 7.4 Reporter: Van Halbert Assignee: Steven Hawkins Provide something like an ECHO statement in the procedure language that can assist a user in debugging their procedure logic -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1625) SalesForce INCLUDE function not being pushed to source

by Paul Nittel (JIRA)

SalesForce INCLUDE function not being pushed to source ------------------------------------------------------ Key: TEIID-1625 URL: https://issues.jboss.org/browse/TEIID-1625 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Environment: Models built by JBDS 4.1 CR1 Reporter: Paul Nittel Assignee: Steven Hawkins While executing the SalesForce test script I executed the following query: Select Name, Communication_Preferences__c from Contact where true = includes(Communication_Preferences__c, 'Fax,Email') Other queries do succeed, but the exclude function suffers a similar fate. The response was: Function includes is marked in the function metadata as a function that must be evaluated at the source. Looking at the functions in the Designer, the PUSH DOWN property has a value of REQUIRED. Am attaching the server log excerpt and Model Project Set -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1603) BQT Query not returning expected row count

by Warren Gibson (JIRA)

BQT Query not returning expected row count ------------------------------------------ Key: TEIID-1603 URL: https://issues.jboss.org/browse/TEIID-1603 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Environment: Running BQT Query Suite against Teiid 7.4 Reporter: Warren Gibson Assignee: Steven Hawkins Attachments: RDBMS_Test_Queries_9600_TestQuery63.xml Teiid 7.4 - the following query is returning no rows but the expected row count is 47 rows. This was tested with MySql50 and Teradata12. I verified the query produced 47 rows with SOA-P 5.1 GA. See expected query results file attached. VDB can be made available if needed. SELECT INTKEY, DATEVALUE, BYTENUM FROM BQT1.SmallA WHERE DATEVALUE <> ANY (SELECT DATEVALUE FROM BQT1.SmallA WHERE BYTENUM >= '-108') The source query from the log file is: SELECT cast(g_0.INTKEY AS signed) AS c_0, g_0.DATEVALUE AS c_1, g_0.BYTENUM AS c_2 FROM smalla AS g_0 WHERE g_0.DATEVALUE NOT IN (SELECT g_1.DATEVALUE FROM smalla AS g_1 WHERE g_1.BYTENUM >= -108) LIMIT 100 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1619) Deprecate MAKEDEP/MAKENOTDEP keyword hints

by Steven Hawkins (JIRA)

Deprecate MAKEDEP/MAKENOTDEP keyword hints ------------------------------------------ Key: TEIID-1619 URL: https://issues.jboss.org/browse/TEIID-1619 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.4.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1 The MAKEDEP/MAKENOTDEP hints should not need to be parsed as keywords, they could just as easily be part of the the same hint as the optional join. e.g. instead of "FROM tbl MAKEDEP ...", you would use "FROM /*+ MAKEDEP */ tbl ..." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1536) Local connections should use calling thread

by Steven Hawkins (JIRA)

Local connections should use calling thread ------------------------------------------- Key: TEIID-1536 URL: https://issues.jboss.org/browse/TEIID-1536 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 locsl connections block on jdbc operations, but mostly do not use the calling thread in the engine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1617) Incorrect rewrite of subquery

by Steven Hawkins (JIRA)

Incorrect rewrite of subquery ----------------------------- Key: TEIID-1617 URL: https://issues.jboss.org/browse/TEIID-1617 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 7.4.1 when performing a semi-join against a query with a key preserved in the semi join criteria and a non-distinct subquery the planner will incorrectly created an unnested query that does not preserve the semi-join. This can happen with either the explicit mj hint or with the query unnesting property set. e.g. select col2 from tbl where keyCol IN (select dupCol from tbl2) will become select col2 from tbl, tbl2 where keyCol = tbl2 rather than select col2 from tbl, (select distinct dupCol from tbl2) x where keyCol = tbl2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1650) hsql does not generally support catalog identifier parts

by Steven Hawkins (JIRA)

hsql does not generally support catalog identifier parts -------------------------------------------------------- Key: TEIID-1650 URL: https://issues.jboss.org/browse/TEIID-1650 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1 hsql does not general support the catalog name component, for example: DELETE FROM "PUBLIC"."PRODUCT" WHERE "PUBLIC"."PRODUCT"."ID" = 2000 will fail, where as DELETE FROM "PUBLIC"."PRODUCT" WHERE "PRODUCT"."ID" = 2000 will succeed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2011