[JBoss JIRA] (TEIIDDES-2684) SalesForce importer issue
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2684:
----------------------------------------
So, If I understood correctly [~shawkins] thinks this is a designer importer logic issue. Basically, the issue was fixed in the importer on server and it needs to be fixed in the importer in Designer, am I right?
To answer your question Steven, yes the "Group does not exist..." error is from a different query in my opinion.
[~blafond] The query works with the dynamic VDB, so I think that indicates that this is a design time issue if it doesn't work with the TD VDB.
> SalesForce importer issue
> -------------------------
>
> Key: TEIIDDES-2684
> URL: https://issues.jboss.org/browse/TEIIDDES-2684
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 10.0.1, 9.2.1
>
> Attachments: salesdynamic-vdb.xml, TEIIDDES_2684.log
>
>
> According to conversation in TEIID-3112 this is a Designer issue. If I understood correctly, it has been fixed in Teiid and now the changes have to be made in TD SF importer.
> I have a VDB with Source model that is created via SalesForce importer and I am getting 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".Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> It works without problems with dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2684) SalesForce importer issue
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2684:
------------------------------------------
It looks like there are multiple issues that are being discussed here. I don't think there is a scenario here where the runtime resolving logic is different. Whether imported through the Designer or Teiid, Salesforce will always have a Campaign table.
The original issue is that the Designer importer logic for is not out of synch with Teiid - which incorporates TEIID-3112 and other changes. So there will be queries that execute correctly using a dynamic vdb, that result in a source error (not a resolving error) with a Designer VDB.
The error "Group does not exist: SalesForceSource.Campaign AS Campaign" doesn't match the debug plan. Is that from a different user query?
> SalesForce importer issue
> -------------------------
>
> Key: TEIIDDES-2684
> URL: https://issues.jboss.org/browse/TEIIDDES-2684
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 10.0.1, 9.2.1
>
> Attachments: salesdynamic-vdb.xml, TEIIDDES_2684.log
>
>
> According to conversation in TEIID-3112 this is a Designer issue. If I understood correctly, it has been fixed in Teiid and now the changes have to be made in TD SF importer.
> I have a VDB with Source model that is created via SalesForce importer and I am getting 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".Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> It works without problems with dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2684) SalesForce importer issue
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2684:
----------------------------------------
,[~mmakovy] Designer's T-editor is parsing and resolving the query and creating a viable/error-free VDB. Once deployed, the runtime resolver is failing on that same SQL.
1) Designer's parsing and resolving logic could be out of sync with the runtime because we do fork the runtime query engine logic with each release
2) If this query could be added to the runtime's unit tests, it could be verified that it is a design-time issue or not, which would probably be much easier than differencing the large amount of SQL query source code.
> SalesForce importer issue
> -------------------------
>
> Key: TEIIDDES-2684
> URL: https://issues.jboss.org/browse/TEIIDDES-2684
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 10.0.1, 9.2.1
>
> Attachments: salesdynamic-vdb.xml, TEIIDDES_2684.log
>
>
> According to conversation in TEIID-3112 this is a Designer issue. If I understood correctly, it has been fixed in Teiid and now the changes have to be made in TD SF importer.
> I have a VDB with Source model that is created via SalesForce importer and I am getting 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".Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> It works without problems with dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2684) SalesForce importer issue
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2684.
----------------------------------
> SalesForce importer issue
> -------------------------
>
> Key: TEIIDDES-2684
> URL: https://issues.jboss.org/browse/TEIIDDES-2684
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 10.0.1, 9.2.1
>
> Attachments: salesdynamic-vdb.xml, TEIIDDES_2684.log
>
>
> According to conversation in TEIID-3112 this is a Designer issue. If I understood correctly, it has been fixed in Teiid and now the changes have to be made in TD SF importer.
> I have a VDB with Source model that is created via SalesForce importer and I am getting 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".Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> It works without problems with dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2684) SalesForce importer issue
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2684:
-----------------------------------
Comment: was deleted
(was: [~shawkins] Could you please take a look at this? Is this a server issue ?
I can still see this error when I am trying to query a VDB created in designer)
> SalesForce importer issue
> -------------------------
>
> Key: TEIIDDES-2684
> URL: https://issues.jboss.org/browse/TEIIDDES-2684
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 10.0.1, 9.2.1
>
> Attachments: salesdynamic-vdb.xml, TEIIDDES_2684.log
>
>
> According to conversation in TEIID-3112 this is a Designer issue. If I understood correctly, it has been fixed in Teiid and now the changes have to be made in TD SF importer.
> I have a VDB with Source model that is created via SalesForce importer and I am getting 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".Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> It works without problems with dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2829) Issues with generated dynamic VDB for preview
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2829?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2829.
----------------------------------
I am not able to reproduce this issue but I am able to preview account table which contains default value and foreign key so that I have closed this issue.
> Issues with generated dynamic VDB for preview
> ---------------------------------------------
>
> Key: TEIIDDES-2829
> URL: https://issues.jboss.org/browse/TEIIDDES-2829
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.1
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Labels: verified_jbdsis-9.0.1
> Fix For: 10.0.1
>
>
> Imported from SF then tried to preview the Accounts table. The generated dynamic VDB (attached) will not deploy.
> 1) 'Default value' property = Generated upon completion
> Results in following deployment error
> TEIID50036 VDB PREVIEW_SFModel_Account.1 model "SFModel" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "NOT NULL DEFAULT [*]Generated[*] upon completion" at line 3, column 40.
> 2) includes FK defns which result in this:
> [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name.
> [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name.
> [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name.
> [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40073 The metadata for the VDB PREVIEW_SFModel_Account.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
> [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB PREVIEW_SFModel_Account.1 is set to FAILED
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2829) Issues with generated dynamic VDB for preview
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2829?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2829:
-----------------------------------
Labels: verified_jbdsis-9.0.1 (was: )
> Issues with generated dynamic VDB for preview
> ---------------------------------------------
>
> Key: TEIIDDES-2829
> URL: https://issues.jboss.org/browse/TEIIDDES-2829
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.1
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Labels: verified_jbdsis-9.0.1
> Fix For: 10.0.1
>
>
> Imported from SF then tried to preview the Accounts table. The generated dynamic VDB (attached) will not deploy.
> 1) 'Default value' property = Generated upon completion
> Results in following deployment error
> TEIID50036 VDB PREVIEW_SFModel_Account.1 model "SFModel" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "NOT NULL DEFAULT [*]Generated[*] upon completion" at line 3, column 40.
> 2) includes FK defns which result in this:
> [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name.
> [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name.
> [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name.
> [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40073 The metadata for the VDB PREVIEW_SFModel_Account.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
> [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB PREVIEW_SFModel_Account.1 is set to FAILED
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months