October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3653) Create examples for the following web data sources

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3653?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-3653: ------------------------------- Fix Version/s: 9.0 > Create examples for the following web data sources > -------------------------------------------------- > > Key: TEIID-3653 > URL: https://issues.jboss.org/browse/TEIID-3653 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts > Reporter: Van Halbert > Assignee: Kylin Soong > Fix For: 9.0 > > > Create examples for the following web data sources: > LinkedIn, Twitter, Facebook, Wikipedia, and Data.gov -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3747: ---------------------------------- Fix Version/s: 8.12 > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12 > > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3112) Incorrect plural name with parent to child join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3112: --------------------------------------- > This should be fixed in dv6.2, am I right ? You first need to clarify whose issue this is. The salesforce changes here also rely on import/metadata changes. So if you start with a dynamic vdb or the Teiid connection importer and can reproduce the above, then it's a Teiid issue. If you are performing an import through Teiid Designer's salesforce importer, then it's their issue. > Incorrect plural name with parent to child join > ----------------------------------------------- > > Key: TEIID-3112 > URL: https://issues.jboss.org/browse/TEIID-3112 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9, 8.7.2, 8.7.1.6_2 > > > The salesforce logic assumes the plural name can be created with just an 's' at the end, however objects such as Opportunity do not follow that pattern. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3112) Incorrect plural name with parent to child join

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ] Matus Makovy edited comment on TEIID-3112 at 10/12/15 3:16 AM: --------------------------------------------------------------- Today I tried to reproduce other bug(originaly reported for Teiid Designer) with DV 6.2 (GA), but I got this error: {quote} Didn't understand relationship 'Opportunitys' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names {quote} when trying to submit this query: {quote} select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32 {quote} This should be fixed in dv6.2, am I right ? was (Author: mmakovy): Today I tried to reproduce other bug(originaly reported for Teiid Designer) with DV 6.2 (GA), but I got this error: ??Didn't understand relationship 'Opportunitys' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names?? when trying to submit this query: ?? select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32?? This should be fixed in dv6.2, am I right ? > Incorrect plural name with parent to child join > ----------------------------------------------- > > Key: TEIID-3112 > URL: https://issues.jboss.org/browse/TEIID-3112 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9, 8.7.2, 8.7.1.6_2 > > > The salesforce logic assumes the plural name can be created with just an 's' at the end, however objects such as Opportunity do not follow that pattern. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3112) Incorrect plural name with parent to child join

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ] Matus Makovy reopened TEIID-3112: --------------------------------- Today I tried to reproduce other bug(originaly reported for Teiid Designer) with DV 6.2 (GA), but I got this error: ??Didn't understand relationship 'Opportunitys' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names?? when trying to submit this query: ?? select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32?? This should be fixed in dv6.2, am I right ? > Incorrect plural name with parent to child join > ----------------------------------------------- > > Key: TEIID-3112 > URL: https://issues.jboss.org/browse/TEIID-3112 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9, 8.7.2, 8.7.1.6_2 > > > The salesforce logic assumes the plural name can be created with just an 's' at the end, however objects such as Opportunity do not follow that pattern. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3494) TABLE() can execute in parallel

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3494?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3494: ---------------------------------- Fix Version/s: 9.0 (was: 8.12) > TABLE() can execute in parallel > ------------------------------- > > Key: TEIID-3494 > URL: https://issues.jboss.org/browse/TEIID-3494 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 9.0 > > > it would be nice if the TABLE() construct was extended to support parallel source executions in the same way that joins can be executed in parallel. - See more at: https://developer.jboss.org/thread/259330#sthash.YjQyw4vR.dpuf -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3531) Better planning of bushy join trees

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3531?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3531: ---------------------------------- Fix Version/s: 9.x (was: 8.12) > Better planning of bushy join trees > ----------------------------------- > > Key: TEIID-3531 > URL: https://issues.jboss.org/browse/TEIID-3531 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.x > > > The primary join planning logic considers left linear trees. We also have a hint to preserve structure and some planning that reuses existing subtrees, but nothing general around considering bushy trees. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3673) Subquery field with limit giving a wrong JDBC SQL in Oracle

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3673?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3673. --------------------------------- > Subquery field with limit giving a wrong JDBC SQL in Oracle > ------------------------------------------------------------ > > Key: TEIID-3673 > URL: https://issues.jboss.org/browse/TEIID-3673 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Mark Tawk > Assignee: Steven Hawkins > Fix For: 8.12 > > > i'm executing the following query using Teiid 8.11.3 and Oracle translator: > select "Trx_LjM_030915"."CID" as "Trx_LjM_030915_CID" > ,"Trx_LjM_030915"."TransactionDate" as "Trx_LjM_030915_TransactionDa" > ,(select "Trx_LjM_030915_sub"."TransactionDate" as "Trx_LjM_030915_TransactionDa" > from "AUDIDATA_SCHEMANAME_MODEL"."AUDIDATA_SCHEMANAME"."Trx_LjM_030915" "Trx_LjM_030915_sub" > where ("Trx_LjM_030915"."CID" = "Trx_LjM_030915_sub"."CID") > AND ( ("Trx_LjM_030915_sub"."TransactionDate" < "Trx_LjM_030915"."TransactionDate") ) > order by "Trx_LjM_030915_sub"."TransactionDate" DESC > LIMIT 0 , 1) as "SubQuery Trx" > from "AUDIDATA_SCHEMANAME_MODEL"."AUDIDATA_SCHEMANAME"."Trx_LjM_030915" "Trx_LjM_030915" LIMIT 0 , 10 > And i'm getting this error: > Error TEIID30504 AUDIDATA_SCHEMANAME_MODELVDB: 904 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT c_0, c_1, c_2 FROM (SELECT g_0."CID" AS c_0, g_0."TransactionDate" AS c_1, (SELECT c_0 FROM (SELECT g_1."TransactionDate" AS c_0 FROM "AUDIDATA_SCHEMANAME"."Trx_LjM_030915" g_1 WHERE g_1."CID" = g_0."CID" AND g_1."TransactionDate" < g_0."TransactionDate" ORDER BY c_0 DESC) WHERE ROWNUM <= 1) AS c_2 FROM "AUDIDATA_SCHEMANAME"."Trx_LjM_030915" g_0) WHERE ROWNUM <= 10 > You can notice g_0."CID" and g_0."TransactionDate" in the where condition are no longer valid in the Teiid generated JDBC SQL; Since they do not exist in the parent query. > Note that the same case works fine with H2 and mysql -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3720) DDLString Visitor not writing the OPTIONS value for Procedure parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3720?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3720. --------------------------------- > DDLString Visitor not writing the OPTIONS value for Procedure parameters > ------------------------------------------------------------------------ > > Key: TEIID-3720 > URL: https://issues.jboss.org/browse/TEIID-3720 > Project: Teiid > Issue Type: Bug > Components: Connector API, Query Engine > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.5 > > > When METADATA properties are set on the Procedure parameters, those are not correctly externalized by the DDLStringVisitor class. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3620) HBase translator - date, time, timestamp values are not translated correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3620?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3620. --------------------------------- > HBase translator - date, time, timestamp values are not translated correctly > ---------------------------------------------------------------------------- > > Key: TEIID-3620 > URL: https://issues.jboss.org/browse/TEIID-3620 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.1.6_2 > Environment: Hbase: 1.1.1 > Phoenix: 4.5.0-HBase-1.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.12 > > Attachments: insert.log, select.log, update.log > > > Using date/time/timestamp value in SQL query causes an exception [1] - {ts '...'}/{d '...'}/{t '...'} is not supported by Phoenix Driver.The issue is present in all types of statements (select, insert, update). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015