August 2013 - teiid-issues - Jboss List Archives

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2625?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2625: --------------------------------------- Given that this works with 8.1 unless you can reproduce this on a later version I will go ahead and mark this issue as out of date. > 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. > One thing to note is that the same query on 7.7 works when the databases > are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? > 8/15: Confirmed the problem occurs for both DB2 and Datacom translators. > Any advice would be appreciated as this is affected a customer installation. > 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-2628) StackOverflowError Running Query Against REST Service

by Ted Jones (JIRA)

Ted Jones created TEIID-2628: -------------------------------- Summary: StackOverflowError Running Query Against REST Service Key: TEIID-2628 URL: https://issues.jboss.org/browse/TEIID-2628 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 8.4 Reporter: Ted Jones Assignee: Steven Hawkins When executing a query against https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/Fligh..., I get the following exception (with query plan included): https://gist.github.com/tejones/6250290 -- 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 commented on TEIID-2625: ----------------------------------- Note also that this problem only appears when the joined table is in a different database and therefore the join cannot be pushed down. > 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. > One thing to note is that the same query on 7.7 works when the databases > are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? > 8/15: Confirmed the problem occurs for both DB2 and Datacom translators. > Any advice would be appreciated as this is affected a customer installation. > 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-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2035: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 985578|https://bugzilla.redhat.com/show_bug.cgi?id=985578] from NEW to MODIFIED > 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, 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 commented on TEIID-2625: ----------------------------------- Correct this works on 8.1 but not our previous release which runs with 7.7. The problem does not seem to be related to the use of the rtrim predicate because I can remove that such that the ON criteria is: "CJORUS_J0.sysid = cx2.sysid and CHORUS_J0.userid = CHORUS_B.evtuserid " and the "and CHORUS_J0.userid = CHORUS_B.evtuserid" portion still gets dropped from the 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 > 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. > One thing to note is that the same query on 7.7 works when the databases > are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? > 8/15: Confirmed the problem occurs for both DB2 and Datacom translators. > Any advice would be appreciated as this is affected a customer installation. > 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 Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2625?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2625: --------------------------------------- To clarify are you saying that this works in 8.1? If not were you able to reproduce in a later version or confirm that it's TEII-2190? > 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. > One thing to note is that the same query on 7.7 works when the databases > are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? > 8/15: Confirmed the problem occurs for both DB2 and Datacom translators. > Any advice would be appreciated as this is affected a customer installation. > 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-2618) Add Example of SAP connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2618?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2618. ----------------------------------- Fix Version/s: 8.4.1 8.5 Resolution: Done Updated the ws.xml with all properties as Ramesh was suggesting. > Add Example of SAP connection > ----------------------------- > > Key: TEIID-2618 > URL: https://issues.jboss.org/browse/TEIID-2618 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.4 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.4.1, 8.5 > > > Add an example of connecting to SAP such as: > <resource-adapter id="sapDS"> > <module slot="main" id="org.jboss.teiid.resource-adapter.webservice"/> > <connection-definitions> > <connection-definition class-name="org.teiid.resource.adapter.ws.WSManagedConnectionFactory" jndi-name="java:/sapDS" enabled="true" use-java-context="true" pool-name="sapDS"> > <config-property name="AuthUserName"> > xxxxxxxxxxx > </config-property> > <config-property name="SecurityType"> > HTTPBasic > </config-property> > <config-property name="RequestTimeout"> > 240000 > </config-property> > <config-property name="EndPoint"> https://sapes1.sapdevcenter.com/sap/opu/odata/sap/ZCD204_EPM_DEMO_SRV/ > </config-property> > <config-property name="AuthPassword"> > xxxxxxxxxxx > </config-property> > </connection-definition> > </connection-definitions> > </resource-adapter> -- 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-2627) Accumulo as a Supported Data Source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2627?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2627: ---------------------------------- Fix Version/s: Open To Community > Accumulo as a Supported Data Source > ----------------------------------- > > Key: TEIID-2627 > URL: https://issues.jboss.org/browse/TEIID-2627 > Project: Teiid > Issue Type: Feature Request > Components: Connector API > Affects Versions: 8.6 > Reporter: devin pinkston > Assignee: Steven Hawkins > Labels: accumulo, data_source > Fix For: Open To Community > > > Support for Accumulo as a data source in Teiid. Would require Resource Adapter and Translator development. -- 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-2627) Accumulo as a Supported Data Source

by devin pinkston (JIRA)

devin pinkston created TEIID-2627: ------------------------------------- Summary: Accumulo as a Supported Data Source Key: TEIID-2627 URL: https://issues.jboss.org/browse/TEIID-2627 Project: Teiid Issue Type: Feature Request Components: Connector API Affects Versions: 8.6 Reporter: devin pinkston Assignee: Steven Hawkins Support for Accumulo as a data source in Teiid. Would require Resource Adapter and Translator development. -- 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. One thing to note is that the same query on 7.7 works when the databases are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? 8/15: Confirmed the problem occurs for both DB2 and Datacom translators. Any advice would be appreciated as this is affected a customer installation. 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. One thing to note is that the same query on 7.7 works when the databases are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? Any advice would be appreciated as this is affected a customer installation. Thanks! Jeff > 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. > One thing to note is that the same query on 7.7 works when the databases > are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? > 8/15: Confirmed the problem occurs for both DB2 and Datacom translators. > Any advice would be appreciated as this is affected a customer installation. > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2013