October 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3092) error with xml project minimization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3092?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3092. --------------------------------- > error with xml project minimization > ----------------------------------- > > Key: TEIID-3092 > URL: https://issues.jboss.org/browse/TEIID-3092 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > The project minimization logic will not look at the appropriate parent chain for each binding and can result in dropping columns that are used from the query which would be seen at runtime as a value not available from context exception. This became apparent with TEIID-3081 where the map order changed in different vms. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2870) Expand "allow-join" extension property on Foreign Key

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2870?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2870. --------------------------------- > Expand "allow-join" extension property on Foreign Key > ----------------------------------------------------- > > Key: TEIID-2870 > URL: https://issues.jboss.org/browse/TEIID-2870 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.7 > > > Currently "allow-join" property on a Foreign Key, defines if the joins based on that Foreign Key that are valid to push to the source or not, when JOIN capability is turned on at translator level. This feature is used in the MongoDB translator to allow JOINS to pushed to source. > What I have seen is "allow-join" is blanket capability that says it supports all LEFT, RIGHT, INNER and CROSS JOINS. It is useful to define this capability in fine grained manner to allow each kind of JOIN explicitly to control the JOIN behavior. > The need came from MongoDB translator, where INNER,LEFT are possible but CROSS and RIGHT are not. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3016) Add headers parameter to invokeHttp

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3016?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3016. --------------------------------- > Add headers parameter to invokeHttp > ----------------------------------- > > Key: TEIID-3016 > URL: https://issues.jboss.org/browse/TEIID-3016 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > There is a need to set common headers, such as content type and accepts. Since there may be other custom values it probably makes sense to do this as a generic parameter as Ramesh suggests: > call restBDM.invokeHttp(action => 'POST', endpoint => qp, headers=>'ContentType=application/json;Accepts=application/text') -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3062) Apply LIMIT 1 optimization for DISTINCT in UNION situations

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3062?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3062. --------------------------------- > Apply LIMIT 1 optimization for DISTINCT in UNION situations > ----------------------------------------------------------- > > Key: TEIID-3062 > URL: https://issues.jboss.org/browse/TEIID-3062 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.1 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.9 > > > The translator does not support select expressions. Query: > SELECT DISTINCT DATAMART_NAME AS c_9, '_constant_' AS c_10 FROM (SELECT datamart_name FROM > ( > SELECT 'DATACOM Datamart' AS DATAMART_NAME FROM SECURITY_DM_DATACOM_DEV_R140_CA31_CMGRD1.VIEWOBJACCESS > UNION ALL > SELECT 'DB2 D91A Datamart' AS DATAMART_NAME FROM SECURITY_DM_DB2_D91APTIB_CMGRD1.VIEWOBJACCESS > ) AS t > ) a > Final part of plan: > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > SortNode(0) output=[datamart_name AS c_9, '_constant_' AS c_10] [DUP_REMOVE] > ProjectNode(1) output=[datamart_name AS c_9, '_constant_' AS c_10] [datamart_name AS c_9, '_constant_' AS c_10] > UnionAllNode(2) output=[datamart_name] > AccessNode(3) output=['DATACOM Datamart' AS DATAMART_NAME] SELECT 'DATACOM Datamart' FROM SECURITY_DM_DATACOM_DEV_R140_CA31_CMGRD1.VIEWOBJACCESS AS g_0 > AccessNode(4) output=['DB2 D91A Datamart' AS DATAMART_NAME] SELECT 'DB2 D91A Datamart' FROM SECURITY_DM_DB2_D91APTIB_CMGRD1.VIEWOBJACCESS AS g_0 > Expected LIMIT 1 in the access nodes. Comment from Steven: "More than likely we are not checking across a union for this optimization." > See https://community.jboss.org/message/883460 for more details and complete plan -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2950) Do not schema-qualify the DDL constraint references if they are within the current schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2950?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2950. --------------------------------- > Do not schema-qualify the DDL constraint references if they are within the current schema > ----------------------------------------------------------------------------------------- > > Key: TEIID-2950 > URL: https://issues.jboss.org/browse/TEIID-2950 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.8, 8.7.1 > > > The DDL constraint statements now contain the model name in order to qualify the schema. For example : > CONSTRAINT FK_Account_ParentId FOREIGN KEY(ParentId) REFERENCES importVDBSrcModel.Account (Id) > Request that the schema be dropped if the reference is within the current schema. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3071) Module needs to be updated for new Saxon-HE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3071?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3071. --------------------------------- > Module needs to be updated for new Saxon-HE > ------------------------------------------- > > Key: TEIID-3071 > URL: https://issues.jboss.org/browse/TEIID-3071 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.9 > Reporter: Tom Arnold > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.9 > > > Teiid built from GIT does not deploy because the bundled Saxon HE JAR does not match what is specified in module xml. > See [here|https://github.com/teiid/teiid/blob/master/build/kits/jboss-as7/modu...]. > Should be changed to something like: > {code:xml} > <resource-root path="Saxon-HE-${version.net.sf.saxon}.jar" /> > {code} > Related to TEIID-3030. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3109) Duplicate key on matpg_relatt

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3109?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3109. --------------------------------- > Duplicate key on matpg_relatt > ----------------------------- > > Key: TEIID-3109 > URL: https://issues.jboss.org/browse/TEIID-3109 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > When a constraint has the same name as a table, the will be a duplicate entry as a primary key on the matpg_relatt table. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2934) OData improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2934?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2934. --------------------------------- > OData improvements > ------------------ > > Key: TEIID-2934 > URL: https://issues.jboss.org/browse/TEIID-2934 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8, 8.7.1 > > > We should only use scrolling when performing caching and we should ensure that the cache entries are being created - either by reading the whole resultset or by adding read all functionality to the cache hint. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2902) More incremental join when a limit is present

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2902?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2902. --------------------------------- > More incremental join when a limit is present > --------------------------------------------- > > Key: TEIID-2902 > URL: https://issues.jboss.org/browse/TEIID-2902 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.7 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Fix For: 8.8 > > > For SQL like: > SELECT > t1.column1, > t2.column1 > FROM > schema1.table1 t1, > schema2.table1 t2 > WHERE > t1.column2=t2.column2 > LIMIT 100 > Teiid may get the whole schema1.table1 content and the whole schema2.table1 content, do the join in memory and then, limit the resultset to 100 records. > However, I think teiid can fetch smaller set of data then do a join. If the join result set is less than number of rows asking, keep fetching next set of data and do a join until hits the limit number. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2925) "driver-name" property missing for resource-adapters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2925?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2925. --------------------------------- > "driver-name" property missing for resource-adapters > ---------------------------------------------------- > > Key: TEIID-2925 > URL: https://issues.jboss.org/browse/TEIID-2925 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7 > > > For resource-adapter that are module based the "driver-name" property is missing, so it becomes cumbersome to match with its original type after the connection factory creation. > Admin API should provide a way when getDataSource(...) is called, "driver-name" must be always present -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014