[JBoss JIRA] (TEIID-5854) Remove SYS.getXMLSchemas
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5854:
-------------------------------------
Summary: Remove SYS.getXMLSchemas
Key: TEIID-5854
URL: https://issues.jboss.org/browse/TEIID-5854
Project: Teiid
Issue Type: Task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 13.0
The deprecated procedure can safely be removed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5853) Solr Connector builder url null
by german tejero (Jira)
german tejero created TEIID-5853:
------------------------------------
Summary: Solr Connector builder url null
Key: TEIID-5853
URL: https://issues.jboss.org/browse/TEIID-5853
Project: Teiid
Issue Type: Bug
Components: Connector API
Affects Versions: 12.3.1
Reporter: german tejero
Assignee: Steven Hawkins
Solr JCA connector does not pass the configured url
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIIDSB-138) Openapi metadata from odata has invalid paths
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-138:
--------------------------------------
Summary: Openapi metadata from odata has invalid paths
Key: TEIIDSB-138
URL: https://issues.jboss.org/browse/TEIIDSB-138
Project: Teiid Spring Boot
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Fix For: 1.3.0
The uri passed into the openapihandler is relative to the context, so the basepath (v2 metadata) is given as an empty string, or the server url (v3 metadata) does not include the context. Either way the resulting doc is invalid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5850) DDL server and foreign data wrapper handling is unclear
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5850?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5850:
---------------------------------------
So the proposal here is to:
1. Don't require CREATE FOREIGN DATA WRAPPER salesforce - by a vendor like pg that creates a dummy fdw. Instead we should just skip directly to:
CREATE FOREIGN DATA WRAPPER mysalesforce TYPE salesforce ...
We can consider using the term HANDLER in addition to or instead of TYPE here. That somewhat aligns with pg.
2. Better document what properties are supported when - only resource-name on create server, and no properties if you create a "dummy" fdw.
> DDL server and foreign data wrapper handling is unclear
> -------------------------------------------------------
>
> Key: TEIID-5850
> URL: https://issues.jboss.org/browse/TEIID-5850
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 13.0, 12.2.2, 12.3.1
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> CREATE server statements in DDL are effectively ignored in the conversion to runtime state - they are simply validated. Similarly a CREATE foreign data wrapper statement that does not specify a type is ignored.
> Attempting to do something like:
> {code}
> CREATE FOREIGN DATA WRAPPER salesforce;
> CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce', supportsOrderBy true);
> {code}
> or
> {code}
> CREATE FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderBy true);
> CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce');
> {code}
> will not result in supportsOrderBy being set on the translator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5851) teiid rename table in salesforce
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5851?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5851.
-----------------------------------
Resolution: Explained
> teiid rename table in salesforce
> --------------------------------
>
> Key: TEIID-5851
> URL: https://issues.jboss.org/browse/TEIID-5851
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> In example project connected to SF i have a table named "User" in SF but "User_" in teiid metadata.
> And another strange behavior is: system tables from teiid as GEOGRAPHY_COLUMNS
> GEOMETRY_COLUMNS placed in teiid server to same schema as Salesforce tables. May be "User_" named because we have same name in teiid metadata system names?
> So, select "SELECT Id, User.FirstName, User.LastName FROM Task LEFT OUTER JOIN User ON User.Id=Task.OwnerId" do not working.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5846) Support "order by" by default in the salesforce translator
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5846?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5846:
---------------------------------------
Sorry didn't see you're follow up. Should be supportsOrderBy true, not false. Too much copy and pasting.
> Support "order by" by default in the salesforce translator
> ----------------------------------------------------------
>
> Key: TEIID-5846
> URL: https://issues.jboss.org/browse/TEIID-5846
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Environment: teiid-spring-boot+spring-odata teiid+spring-data-salesforce
> Reporter: Renat Eskenin
> Priority: Major
> Fix For: 13.1
>
>
> When we call simple request as
> salesforce-odata-facade/odata/salesforce/Product_License__c?$top=1&$select=Id
> request processing time is 1min. But this request processing by simple SOAP SOQL request is ~150ms.
> I think this do because teiid select all objects by ignoring top in request.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5846) Support "order by" by default in the salesforce translator
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5846?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-5846 at 11/20/19 8:31 AM:
-----------------------------------------------------------------
Renat, there is an underlying bug in the ddl handling that is preventing the property from being set. Please see TEIID-5850.
The workaround is to do something like:
{code}
CREATE FOREIGN DATA WRAPPER salesforce;
CREATE FOREIGN DATA WRAPPER mysalesforce type salesforce OPTIONS (supportsOrderBy true);
CREATE SERVER salesforce FOREIGN DATA WRAPPER mysalesforce OPTIONS ("resource-name" 'salesforce');
{code}
So that there is explicitly an "override" translator that sets the property.
was (Author: shawkins):
Renat, there is an underlying bug in the ddl handling that is preventing the property from being set. Please see TEIID-5850.
The workaround is to do something like:
{code}
CREATE FOREIGN DATA WRAPPER salesforce;
CREATE FOREIGN DATA WRAPPER mysalesforce type salesforce OPTIONS (supportsOrderBy false);
CREATE SERVER salesforce FOREIGN DATA WRAPPER mysalesforce OPTIONS ("resource-name" 'salesforce');
{code}
So that there is explicitly an "override" translator that sets the property.
> Support "order by" by default in the salesforce translator
> ----------------------------------------------------------
>
> Key: TEIID-5846
> URL: https://issues.jboss.org/browse/TEIID-5846
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Environment: teiid-spring-boot+spring-odata teiid+spring-data-salesforce
> Reporter: Renat Eskenin
> Priority: Major
> Fix For: 13.1
>
>
> When we call simple request as
> salesforce-odata-facade/odata/salesforce/Product_License__c?$top=1&$select=Id
> request processing time is 1min. But this request processing by simple SOAP SOQL request is ~150ms.
> I think this do because teiid select all objects by ignoring top in request.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month