[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... ]
Work on TEIID-5850 started by Steven Hawkins.
---------------------------------------------
> 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-5848) views in vertica not found by teiid
by Renat Eskenin (Jira)
[ https://issues.jboss.org/browse/TEIID-5848?page=com.atlassian.jira.plugin... ]
Renat Eskenin commented on TEIID-5848:
--------------------------------------
Im using version 1.2. Please write latest stable version and i will use it. No snapshots, nopasaran! :)
> views in vertica not found by teiid
> -----------------------------------
>
> Key: TEIID-5848
> URL: https://issues.jboss.org/browse/TEIID-5848
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> We created view in vertica DB
> Example project with vertica translator+odata not found this view
> {code}
> src 1 Varchar 4 [NULL] true false false [NULL] false [NULL]
> src_id 2 Varchar 18 [NULL] true false false [NULL] false [NULL]
> src_name 3 Varchar 363 [NULL] true false false [NULL] false [NULL]
> account_id 4 Varchar 18 [NULL] true false false [NULL] false [NULL]
> name 5 Varchar 765 [NULL] true false false [NULL] false [NULL]
> billing_country 6 Varchar 240 [NULL] true false false [NULL] false [NULL]
> root_domain 7 Varchar 192 [NULL] true false false [NULL] false [NULL]
> sales_team 8 Varchar 240 [NULL] true false false [NULL] false [NULL]
> {code}
> {
> "error": {
> "code": null,
> "message": "Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'funnel_leads'."
> }
> }
> But regular tables works properly
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5848) views in vertica not found by teiid
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5848?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5848:
---------------------------------------
> And get the result!
That's progress!
> External JDBC connection with property teiid.host-name=127.0.0.1 do not working too
Are you using teiid spring boot 1.2 or a later snapshot?
> But how to get this result in odata request?
I don't think that it's possible without using a vdb in this case. You'll need the vdb to issue an alter to add a key to funnel_leads:
{code}
CREATE DATABASE db;
USE DATABASE db;
CREATE FOREIGN DATA WRAPPER vertica;
CREATE SERVER vertica FOREIGN DATA WRAPPER vertica;
CREATE SCHEMA vertica SERVER vertica;
IMPORT FROM SERVER vertica INTO vertica OPTIONS("importer.useFullSchemaName" 'false');
SET SCHEMA vertica;
ALTER view funnel_leads ADD primary key (src_id, account_id);
{code}
> views in vertica not found by teiid
> -----------------------------------
>
> Key: TEIID-5848
> URL: https://issues.jboss.org/browse/TEIID-5848
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> We created view in vertica DB
> Example project with vertica translator+odata not found this view
> {code}
> src 1 Varchar 4 [NULL] true false false [NULL] false [NULL]
> src_id 2 Varchar 18 [NULL] true false false [NULL] false [NULL]
> src_name 3 Varchar 363 [NULL] true false false [NULL] false [NULL]
> account_id 4 Varchar 18 [NULL] true false false [NULL] false [NULL]
> name 5 Varchar 765 [NULL] true false false [NULL] false [NULL]
> billing_country 6 Varchar 240 [NULL] true false false [NULL] false [NULL]
> root_domain 7 Varchar 192 [NULL] true false false [NULL] false [NULL]
> sales_team 8 Varchar 240 [NULL] true false false [NULL] false [NULL]
> {code}
> {
> "error": {
> "code": null,
> "message": "Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'funnel_leads'."
> }
> }
> But regular tables works properly
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5846) top in odata query is not working
by Renat Eskenin (Jira)
[ https://issues.jboss.org/browse/TEIID-5846?page=com.atlassian.jira.plugin... ]
Renat Eskenin commented on TEIID-5846:
--------------------------------------
DDL
{code}
CREATE DATABASE db;
USE DATABASE db;
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');
CREATE SCHEMA sf SERVER salesforce;
IMPORT FROM SERVER salesforce INTO sf OPTIONS("importer.useFullSchemaName" 'false');
{code}
LOG
{code}
[2019-11-15 18:38:43,539 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.PROCESSOR [http-nio-8080-exec-1]: Request Thread 8yNyEoQ+lwBm.0 with state NEW
[2019-11-15 18:38:43,539 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.PROCESSOR [http-nio-8080-exec-1]: 8yNyEoQ+lwBm.0 executing prepared /*+ cache(ttl:300000 scope:USER) */ SELECT g0.Id, g0.FiscalYearSettingsId, g0.Type, g0.StartDate, g0.EndDate, g0.IsForecastPeriod, g0.QuarterLabel, g0.PeriodLabel, g0.Number, g0.FullyQualifiedLabel FROM sf.Period AS g0 ORDER BY g0.Id LIMIT ?, ? /* 8yNyEoQ+lwBm */
[2019-11-15 18:38:43,544 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.PROCESSOR [http-nio-8080-exec-1]: ProcessTree for 8yNyEoQ+lwBm.0 LimitNode(0) output=[g0.Id, g0.FiscalYearSettingsId, g0.Type, g0.StartDate, g0.EndDate, g0.IsForecastPeriod, g0.QuarterLabel, g0.PeriodLabel, g0.Number, g0.FullyQualifiedLabel] limit ? offset ?
SortNode(1) output=[g0.Id, g0.FiscalYearSettingsId, g0.Type, g0.StartDate, g0.EndDate, g0.IsForecastPeriod, g0.QuarterLabel, g0.PeriodLabel, g0.Number, g0.FullyQualifiedLabel] [SORT] [g0.Id]
AccessNode(2) output=[g0.Id, g0.FiscalYearSettingsId, g0.Type, g0.StartDate, g0.EndDate, g0.IsForecastPeriod, g0.QuarterLabel, g0.PeriodLabel, g0.Number, g0.FullyQualifiedLabel] SELECT sf.Period.Id, sf.Period.FiscalYearSettingsId, sf.Period.Type, sf.Period.StartDate, sf.Period.EndDate, sf.Period.IsForecastPeriod, sf.Period.QuarterLabel, sf.Period.PeriodLabel, sf.Period.Number, sf.Period.FullyQualifiedLabel FROM sf.Period
[2019-11-15 18:38:43,546 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.TXN_LOG [http-nio-8080-exec-1]: before getOrCreateTransactionContext:org.teiid.dqp.internal.process.TransactionServerImpl@599d9381(8yNyEoQ+lwBm)
[2019-11-15 18:38:43,547 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.TXN_LOG [http-nio-8080-exec-1]: after getOrCreateTransactionContext : 8yNyEoQ+lwBm NONE ID:NONE
[2019-11-15 18:38:43,548 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.BUFFER_MGR [http-nio-8080-exec-1]: Creating TupleBuffer: 2 [g0.Id, g0.FiscalYearSettingsId, g0.Type, g0.StartDate, g0.EndDate, g0.IsForecastPeriod, g0.QuarterLabel, g0.PeriodLabel, g0.Number, g0.FullyQualifiedLabel] [class java.lang.String, class java.lang.String, class java.lang.String, class java.sql.Date, class java.sql.Date, class java.lang.Boolean, class java.lang.String, class java.lang.String, class java.lang.Integer, class java.lang.String] batch size 256 of type PROCESSOR
[2019-11-15 18:38:43,550 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.CONNECTOR [http-nio-8080-exec-1]: 8yNyEoQ+lwBm.0.2.0 Create State
[2019-11-15 18:38:43,568 MSK] DEBUG [salesforce-odata-facade,,,] org.teiid.PROCESSOR [Worker0_QueryProcessorQueue0]: Running task for parent thread http-nio-8080-exec-1
[2019-11-15 18:38:43,568 MSK] DEBUG [salesforce-odata-facade,,,] org.teiid.CONNECTOR [Worker0_QueryProcessorQueue0]: 8yNyEoQ+lwBm.0.2.0 Processing NEW request: SELECT sf.Period.Id, sf.Period.FiscalYearSettingsId, sf.Period.Type, sf.Period.StartDate, sf.Period.EndDate, sf.Period.IsForecastPeriod, sf.Period.QuarterLabel, sf.Period.PeriodLabel, sf.Period.Number, sf.Period.FullyQualifiedLabel FROM sf.Period
[2019-11-15 18:38:43,572 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.BUFFER_MGR [http-nio-8080-exec-1]: Creating TupleBuffer: 3 [g0.Id, g0.FiscalYearSettingsId, g0.Type, g0.StartDate, g0.EndDate, g0.IsForecastPeriod, g0.QuarterLabel, g0.PeriodLabel, g0.Number, g0.FullyQualifiedLabel] [class java.lang.String, class java.lang.String, class java.lang.String, class java.sql.Date, class java.sql.Date, class java.lang.Boolean, class java.lang.String, class java.lang.String, class java.lang.Integer, class java.lang.String] batch size 256 of type PROCESSOR
[2019-11-15 18:38:43,572 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.PROCESSOR [http-nio-8080-exec-1]: Created intermediate sort buffer 3
[2019-11-15 18:38:43,572 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.BUFFER_MGR [http-nio-8080-exec-1]: 8yNyEoQ+lwBm.0.2.0 Blocking on source query 8yNyEoQ+lwBm.0.2.0
[2019-11-15 18:38:43,572 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.BUFFER_MGR [http-nio-8080-exec-1]: 8yNyEoQ+lwBm.0 Blocking on source request(s).
[2019-11-15 18:38:43,572 MSK] DEBUG [salesforce-odata-facade,a0a7588791d15c18,a0a7588791d15c18,false] org.teiid.PROCESSOR [http-nio-8080-exec-1]: Request Thread 8yNyEoQ+lwBm.0 - processor blocked
[2019-11-15 18:38:43,765 MSK] DEBUG [salesforce-odata-facade,,,] org.teiid.CONNECTOR [Worker0_QueryProcessorQueue0]: 8yNyEoQ+lwBm.0.2.0 Obtained execution
[2019-11-15 18:38:43,765 MSK] DEBUG [salesforce-odata-facade,,,] org.teiid.COMMAND_LOG.SOURCE [Worker0_QueryProcessorQueue0]: START DATA SRC COMMAND: startTime=2019-11-15 18:38:43.765 requestID=8yNyEoQ+lwBm.0 sourceCommandID=2 executionID=0 txID=null modelName=sf translatorName=mysalesforce sessionID=8yNyEoQ+lwBm principal=sf sql=SELECT sf.Period.Id, sf.Period.FiscalYearSettingsId, sf.Period.Type, sf.Period.StartDate, sf.Period.EndDate, sf.Period.IsForecastPeriod, sf.Period.QuarterLabel, sf.Period.PeriodLabel, sf.Period.Number, sf.Period.FullyQualifiedLabel FROM sf.Period
[2019-11-15 18:38:43,779 MSK] DEBUG [salesforce-odata-facade,,,] org.teiid.CONNECTOR [Worker0_QueryProcessorQueue0]: salesforce.8yNyEoQ+lwBm.8yNyEoQ+lwBm.0.2: Incoming Query: SELECT Period.Id, Period.FiscalYearSettingsId, Period.Type, Period.StartDate, Period.EndDate, Period.IsForecastPeriod, Period.QuarterLabel, Period.PeriodLabel, Period.Number, Period.FullyQualifiedLabel FROM Period
[2019-11-15 18:38:43,788 MSK] DEBUG [salesforce-odata-facade,,,] org.teiid.CONNECTOR [Worker0_QueryProcessorQueue0]: salesforce.8yNyEoQ+lwBm.8yNyEoQ+lwBm.0.2: Executing Query: SELECT Period.Id, Period.FiscalYearSettingsId, Period.Type, Period.StartDate, Period.EndDate, Period.IsForecastPeriod, Period.QuarterLabel, Period.PeriodLabel, Period.Number, Period.FullyQualifiedLabel FROM Period
{code}
> top in odata query is not working
> ---------------------------------
>
> Key: TEIID-5846
> URL: https://issues.jboss.org/browse/TEIID-5846
> Project: Teiid
> Issue Type: Bug
> Components: OData, 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-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 updated TEIID-5850:
----------------------------------
Workaround Description:
Use an intermediate "override" data wrapper:
{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}
> 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-5846) top in odata query is not working
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5846?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5846:
---------------------------------------
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.
> top in odata query is not working
> ---------------------------------
>
> Key: TEIID-5846
> URL: https://issues.jboss.org/browse/TEIID-5846
> Project: Teiid
> Issue Type: Bug
> Components: OData, 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] (TEIIDSB-137) The resource-name concept seems unused
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-137:
--------------------------------------
Summary: The resource-name concept seems unused
Key: TEIIDSB-137
URL: https://issues.jboss.org/browse/TEIIDSB-137
Project: Teiid Spring Boot
Issue Type: Quality Risk
Components: datasource, documentation
Reporter: Steven Hawkins
Fix For: 1.3.0
Most examples show the usage of the resource-name option on create server - however this is not used anywhere in the code. It seems like the intention was to possibly use that name instead of the server name as the bean name, but everywhere makes the assumption that they match.
--
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)
Steven Hawkins created TEIID-5850:
-------------------------------------
Summary: 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
Fix For: 13.0, 12.2.2, 12.3.1
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-5849) Merge the admin and api sub-modules
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5849:
-------------------------------------
Summary: Merge the admin and api sub-modules
Key: TEIID-5849
URL: https://issues.jboss.org/browse/TEIID-5849
Project: Teiid
Issue Type: Task
Components: AdminApi, Connector API
Reporter: Steven Hawkins
Assignee: Steven Hawkins
There isn't a compelling reason to keep the admin and api submodules separate any longer.
api depends on admin already and keeping api code out of admin makes it difficult to evolve the vdb structural components into regular api objects - or at least hold resolved references.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5849) Merge the admin and api sub-modules
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5849?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5849:
----------------------------------
Fix Version/s: 13.0
Original Estimate: 2 hours
Remaining Estimate: 2 hours
Story Points: 1
Sprint: DV Sprint 55
Estimated Difficulty: Low
> Merge the admin and api sub-modules
> -----------------------------------
>
> Key: TEIID-5849
> URL: https://issues.jboss.org/browse/TEIID-5849
> Project: Teiid
> Issue Type: Task
> Components: AdminApi, Connector API
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> There isn't a compelling reason to keep the admin and api submodules separate any longer.
> api depends on admin already and keeping api code out of admin makes it difficult to evolve the vdb structural components into regular api objects - or at least hold resolved references.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month