July 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1524) Index metadata strings container their entire record line.

by Steven Hawkins (JIRA)

Index metadata strings container their entire record line. ---------------------------------------------------------- Key: TEIID-1524 URL: https://issues.jboss.org/browse/TEIID-1524 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 7.4 The strings parsed by the IndexMetadataFactory still contain their entire record line since the substring function is used without creating new strings. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1527) local connection doc provides an invalid example

by Steven Hawkins (JIRA)

local connection doc provides an invalid example ------------------------------------------------ Key: TEIID-1527 URL: https://issues.jboss.org/browse/TEIID-1527 Project: Teiid Issue Type: Quality Risk Components: Documentation Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 The local connection documentation shows a datasource with a min size of 5. If you configure a local connection in this way, then pool startup can error since datasources are deployed before vdbs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1523) Dynamic sql failure with null procedure parameters

by Steven Hawkins (JIRA)

Dynamic sql failure with null procedure parameters -------------------------------------------------- Key: TEIID-1523 URL: https://issues.jboss.org/browse/TEIID-1523 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 Dynamic sql will fail to execute when used in a procedure that has a null input parameter, since it is forming a typeless constant. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1525) update the hibernate usage with a note about id generation

by Steven Hawkins (JIRA)

update the hibernate usage with a note about id generation ---------------------------------------------------------- Key: TEIID-1525 URL: https://issues.jboss.org/browse/TEIID-1525 Project: Teiid Issue Type: Quality Risk Components: Documentation Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1217) Derive VDB Name Using Version During Deployment in Jopr

by Ted Jones (JIRA)

Derive VDB Name Using Version During Deployment in Jopr ------------------------------------------------------- Key: TEIID-1217 URL: https://jira.jboss.org/browse/TEIID-1217 Project: Teiid Issue Type: Feature Request Components: Jopr Plugin Affects Versions: 7.1 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.2 Need to add a configuration to the file based deployment of vdbs that contains version. From this the vdb file name should be derived. For example, if I deploy a vdb called MyVDB.vdb with a version of 3, the derived file name would be MyVDB.3.vdb. -- 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

13 years, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (TEIID-1196) Support Deployment of VDB via a URL in Jopr Plugin

by Ted Jones (JIRA)

Support Deployment of VDB via a URL in Jopr Plugin -------------------------------------------------- Key: TEIID-1196 URL: https://jira.jboss.org/browse/TEIID-1196 Project: Teiid Issue Type: Feature Request Components: Jopr Plugin Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Currently VDB deployment is strictly file based. Need to add support for deployment via URL. Also, when a VDB is deployed through a URL, the the "component name" supplied to the profile service deployer to save your deployment under needs to take a name and version and derive a unique name. -- 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

13 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (TEIID-1483) Resolving changes to consolidate teiid/teiid designer handling

by Steven Hawkins (JIRA)

Resolving changes to consolidate teiid/teiid designer handling -------------------------------------------------------------- Key: TEIID-1483 URL: https://issues.jboss.org/browse/TEIID-1483 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 Designer currently must supply external metadata that should be easily derived by Teiid. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Resolved: (TEIID-1664) Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected BQT results

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1664?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1664. ----------------------------------- Fix Version/s: 7.4.1 7.5 Resolution: Done Marking as resolved. New issues can be opened against Teradata for unsupported expression nesting if needed. > Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected BQT results > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1664 > URL: https://issues.jboss.org/browse/TEIID-1664 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > Attachments: QT_teradata12_Push.vdb > > > Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected results. The following query should be returning 22 rows but 0 rows are returned. > SELECT intkey, booleanvalue FROM BQT1.SmallA WHERE LTRIM(BQT1.SmallA.BooleanValue) = 'true' ORDER BY intkey > However, if the LTRIM is removed like (SELECT intkey, booleanvalue FROM BQT1.SmallA WHERE BQT1.SmallA.BooleanValue = 'true' ORDER BY intkey) 22 rows are returned. > This should be logged against Teiid 7.4.1 > VDB attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-993) Enhance XML processing to execute relational queries in parallel when possible

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-993?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-993. ---------------------------------- Fix Version/s: 7.4.1 Resolution: Done Added logic to look ahead for execsqlinstructions within a program and to init/open the processors - this is the situation when there are sibling mappingclasses at the same document level. For typical query plans, opening them will submit the relevant source queries. The output is still built sequentially. > Enhance XML processing to execute relational queries in parallel when possible > ------------------------------------------------------------------------------ > > Key: TEIID-993 > URL: https://issues.jboss.org/browse/TEIID-993 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.4.1 > > > Per feedback from Barry, was reviewing XML processing and because we execute all queries serially in our XML processing. However, conceptually, we could often execute multiple mapping class and/or temp table queries in parallel. When time permits it might be benefitial to investigate this. > All mapping classes at depth "n" in the document model are independent of each other, so they can be executed in parallel. Each mapping class may have input sets to any ancestor mapping class up to depth "n-1", or may select from any temp table up to depth "n" (the same depth). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-993) Enhance XML processing to execute relational queries in parallel when possible

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-993?page=com.atlassian.jira.plugin.... ] Steven Hawkins reassigned TEIID-993: ------------------------------------ Assignee: Steven Hawkins > Enhance XML processing to execute relational queries in parallel when possible > ------------------------------------------------------------------------------ > > Key: TEIID-993 > URL: https://issues.jboss.org/browse/TEIID-993 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Per feedback from Barry, was reviewing XML processing and because we execute all queries serially in our XML processing. However, conceptually, we could often execute multiple mapping class and/or temp table queries in parallel. When time permits it might be benefitial to investigate this. > All mapping classes at depth "n" in the document model are independent of each other, so they can be executed in parallel. Each mapping class may have input sets to any ancestor mapping class up to depth "n-1", or may select from any temp table up to depth "n" (the same depth). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2011