teiid-designer-issues September 2015

teiid-designer-issues@lists.jboss.org

1 participants
413 discussions

[JBoss JIRA] (TEIIDDES-2619) Salesforce custom URL not added if Datasource is created with Model Info

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2619?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-2619: --------------------------------------- Fix Version/s: 9.0.4 Assignee: Mark Drilling This issue was related to 2579. Verified after the 2579 fix that I could createDataSource using ModelInfo, and the URL was written to the config datasource properties. > Salesforce custom URL not added if Datasource is created with Model Info > ------------------------------------------------------------------------ > > Key: TEIIDDES-2619 > URL: https://issues.jboss.org/browse/TEIIDDES-2619 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 9.0.2 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 9.0.4 > > > Spawning from https://issues.jboss.org/browse/TEIIDDES-2579 regarding Salesforce custom URL. If you run the import with a custom URL, unless you manually create the Data Source with the Connection Profile Info, the Datasource (Resource Adapter) on the server will not contain the custom URL. > So if the customer takes the default on the Create Data Source, which is Model Info or they let Teiid Designer create it when they create the VDB the connection will fail because the custom URL hasn't been written to the server configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2500) Problems with model created via import from Salesforce when using JOIN query

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2500?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2500: ----------------------------------------- I was able to reproduce with both types of VDB, so this does not appear to be a Designer issue. Logged the linked JIRA in teiid for their response. The original query problem logged here appears to have been addressed already in a later teiid version, but I encountered a different issue. > Problems with model created via import from Salesforce when using JOIN query > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2500 > URL: https://issues.jboss.org/browse/TEIIDDES-2500 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Reporter: Matus Makovy > Assignee: Mark Drilling > Fix For: 9.0.4, 9.2 > > Attachments: log, salesdynamic-vdb.xml, SalesforceTD.zip > > > Discovered this issue when trying to verify TEIID-3112 > I am trying to execute this query on VDB created via import from SalesForce in Teiid Designer. > {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} > And I get this exception: > {quote} > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: Invalid QName in mapping: sf:INVALID_TYPE > {quote} > Log attached > With dynamic VDB created manually or with import using Teiid Connection Importer via Designer everything works. > Project from Designer + dynamic VDB attached -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2629) Updating data source import resets translator to jdbc-simple for Netezza

by Bas Piepers (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2629?page=com.atlassian.jira.plu... ] Bas Piepers commented on TEIIDDES-2629: --------------------------------------- [~blafond], not sure if I understand correctly. Of course we created a new connection profile at the beginning and it is possible that we choose Generic JDBC to create a new Driver Profile for Netezza and set the source binding to a jndi entry in standalone.xml afterwards (and the translator name). If that last question is for me: I would say that option 1) is enough. Thanks > Updating data source import resets translator to jdbc-simple for Netezza > ------------------------------------------------------------------------ > > Key: TEIIDDES-2629 > URL: https://issues.jboss.org/browse/TEIIDDES-2629 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Bas Piepers > Priority: Minor > Fix For: 9.2 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png > > > If you update an existing source model while the translator is set to "Netezza", Teiid Designer resets the translator to "jdbc-simple". You have to manually set the translator back to "Netezza". > See "Steps to reproduce" to get a better view of what happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

← Newer
1
...
39
40
41
42
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2015