August 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2625) Part of join criteria is getting ignored

by Jeff Hayes (JIRA)

[ https://issues.jboss.org/browse/TEIID-2625?page=com.atlassian.jira.plugin... ] Jeff Hayes updated TEIID-2625: ------------------------------ Attachment: 7.7_Teiid_SHOWPLAN > Part of join criteria is getting ignored > ---------------------------------------- > > Key: TEIID-2625 > URL: https://issues.jboss.org/browse/TEIID-2625 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.1 > Environment: z/OS JZOS > Reporter: Jeff Hayes > Assignee: Steven Hawkins > Attachments: 7.7_Teiid_SHOWPLAN > > > The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. > Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. > > Please see attached query plan. > Is there a fix for this or workaround for the query? > Thanks! > Jeff > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2625) Part of join criteria is getting ignored

by Jeff Hayes (JIRA)

[ https://issues.jboss.org/browse/TEIID-2625?page=com.atlassian.jira.plugin... ] Jeff Hayes updated TEIID-2625: ------------------------------ Description: The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. Please see attached query plan. Is there a fix for this or workaround for the query? Thanks! Jeff was: The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. Please see attached query plan. > Part of join criteria is getting ignored > ---------------------------------------- > > Key: TEIID-2625 > URL: https://issues.jboss.org/browse/TEIID-2625 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.1 > Environment: z/OS JZOS > Reporter: Jeff Hayes > Assignee: Steven Hawkins > > The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. > Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. > > Please see attached query plan. > Is there a fix for this or workaround for the query? > Thanks! > Jeff > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2625) Part of join criteria is getting ignored

by Jeff Hayes (JIRA)

Jeff Hayes created TEIID-2625: --------------------------------- Summary: Part of join criteria is getting ignored Key: TEIID-2625 URL: https://issues.jboss.org/browse/TEIID-2625 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7.1 Environment: z/OS JZOS Reporter: Jeff Hayes Assignee: Steven Hawkins The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. Please see attached query plan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2035. --------------------------------- Labels: CR1 (was: ) Fix Version/s: 8.4.1 8.5 Resolution: Done Implemented the workaround defined in the thread https://community.jboss.org/message/832363 This solution requires creating a resource-adapter for each connection factory, also when the connection factory is deleted then the resource-adapter also deleted. Once side effect is user uses Admin API it completely will be consistent in creation/deletion of sources, if they mix in editing XML file directly and Admin API some in-consistency is expected the way they are handled. > DeleteDataSource method on Admin API does not completely delete the Connection Factory > -------------------------------------------------------------------------------------- > > Key: TEIID-2035 > URL: https://issues.jboss.org/browse/TEIID-2035 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.4.1, 8.5 > > > ConnectionFactory requires a two step creation process > 1) create the resource-adaptor section > 2) connection factory section > The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2623) When deleting a project from Teiid Designer the associated preview* files are not removed from the server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2623?page=com.atlassian.jira.plugin... ] Steven Hawkins deleted TEIID-2623: ---------------------------------- > When deleting a project from Teiid Designer the associated preview* files are not removed from the server > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-2623 > URL: https://issues.jboss.org/browse/TEIID-2623 > Project: Teiid > Issue Type: Bug > Environment: Eclipse Kepler w/ Teiid Designer 8.2, Mac Mountain Lion OS 10.8.4, Oracle Java 1.7.0_25, EAP 6.1, Teiid 8.4 components on EAP 6 > Reporter: Blaine Mincey > Assignee: Steven Hawkins > > I create a Teiid Model Project with a variety of virtual models. I will select to preview several different views which in turn deploys the PREVIEW* VDBs to EAP 6 while it is running. I then choose to delete my Teiid Model Project. Then, I stop my running EAP 6 server and restart. The PREVIEW* components are still deployed to the server. I was expecting all of these artifacts from my deleted project to be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2624) When deleting a project from Teiid Designer the associated preview* files are not removed from the server

by Blaine Mincey (JIRA)

Blaine Mincey created TEIID-2624: ------------------------------------ Summary: When deleting a project from Teiid Designer the associated preview* files are not removed from the server Key: TEIID-2624 URL: https://issues.jboss.org/browse/TEIID-2624 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.4 Environment: Eclipse Kepler w/ Teiid Designer 8.2, Mac Mountain Lion OS 10.8.4, Oracle Java 1.7.0_25, EAP 6.1, Teiid 8.4 components on EAP 6 Reporter: Blaine Mincey Assignee: Steven Hawkins I create a Teiid Model Project with a variety of virtual models. I will select to preview several different views which in turn deploys the PREVIEW* VDBs to EAP 6 while it is running. I then choose to delete my Teiid Model Project. Then, I stop my running EAP 6 server and restart. The PREVIEW* components are still deployed to the server. I was expecting all of these artifacts from my deleted project to be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2139) Factor out common table expressions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2139?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2139: --------------------------------------- Mark, see TEIID-2507 > Factor out common table expressions > ----------------------------------- > > Key: TEIID-2139 > URL: https://issues.jboss.org/browse/TEIID-2139 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > > Query planner should factor out common table expressions within queries so they are only executed once. See https://community.jboss.org/message/742355 for more context. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2623) When deleting a project from Teiid Designer the associated preview* files are not removed from the server

by Blaine Mincey (JIRA)

Blaine Mincey created TEIID-2623: ------------------------------------ Summary: When deleting a project from Teiid Designer the associated preview* files are not removed from the server Key: TEIID-2623 URL: https://issues.jboss.org/browse/TEIID-2623 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.4 Environment: Eclipse Kepler w/ Teiid Designer 8.2, Mac Mountain Lion OS 10.8.4, Oracle Java 1.7.0_25, EAP 6.1, Teiid 8.4 components on EAP 6 Reporter: Blaine Mincey Assignee: Steven Hawkins I create a Teiid Model Project with a variety of virtual models. I will select to preview several different views which in turn deploys the PREVIEW* VDBs to EAP 6 while it is running. I then choose to delete my Teiid Model Project. Then, I stop my running EAP 6 server and restart. The PREVIEW* components are still deployed to the server. I was expecting all of these artifacts from my deleted project to be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2139) Factor out common table expressions

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2139?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2139: -------------------------------------- Session based materialized views sounds interesting. Is there a JIRA? > Factor out common table expressions > ----------------------------------- > > Key: TEIID-2139 > URL: https://issues.jboss.org/browse/TEIID-2139 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > > Query planner should factor out common table expressions within queries so they are only executed once. See https://community.jboss.org/message/742355 for more context. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- Steve, Here is changes I made so far https://github.com/rareddy/teiid/commit/bec85462a4f551ffe742467626da1221a... Which also includes the VDB startup and shutdown based trigger executions. What this lacks is avoiding two separate requests loading the matviews simultaneously. I am not sure how handle that, as STATUS table updates seemed to be working as READ_COMMITED state and since load happens in atomic block the record does not get updated until the results are loaded. Can you suggest any alternatives, how I may be able to fix this? > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2013