[JBoss JIRA] (TEIID-2605) Optimization substitutes wrong column in where clause
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2605?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2605.
---------------------------------
> Optimization substitutes wrong column in where clause
> -----------------------------------------------------
>
> Key: TEIID-2605
> URL: https://issues.jboss.org/browse/TEIID-2605
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.1
> Environment: z/OS
> Reporter: Jeff Hayes
> Assignee: Steven Hawkins
> Attachments: query_plan.txt, views.xml
>
>
> Optimization results in a query with a different column in the WHERE clause producing an empty result set.
> Full query plan is attached but the beginning and ending queries are shown below. Note that the subject column of the IN clause is SCOPEID but optimization changes it to AUTHID for some reason.
> USER COMMAND:
> SELECT * FROM SECURITY.SCPXREF AS CHORUS_B WHERE (CHORUS_B.SYSID = 'DE29') AND ((CHORUS_B.SCOPEID IN (SELECT SN5.SCOPEID FROM SECURI
> TY.SCPNEXT AS SN5 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN4.SCOPEID FROM SECURITY.SCPNEXT AS SN4 WHERE (SYSID = 'DE29') AND
> (NEXTREC IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURI
> TY.SCPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))))))) OR (CHORUS_B.SCOPEID IN (SELECT SN4.SCOPEID FROM SECURIT
> Y.SCPNEXT AS SN4 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND
> (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURITY.SCPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))))) OR (CHORUS_B.SC
> OPEID IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURITY.S
> CPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))) OR (CHORUS_B.SCOPEID IN (SELECT SN2.SCOPEID FROM SECURITY.SCPNEX
> T AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))) OR (CHORUS_B.SCOPEID = 'CHRDEPT1'))
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(10) output=[x.sysid AS sysid, x.scopeid AS authid, x.authid AS scopeid, x.authtype AS authtype] SELECT g_0.SYSID, g_0.SCO
> PEID, g_0.AUTHID, g_0.AUTHTYPE FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPXREF AS g_0 WHERE (g_0.SYSID = 'DE29') AND ((g_0.AUTHID IN
> (SELECT g_1.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_1 WHERE (g_1.SYSID = 'DE29') AND (g_1.NEXTREC IN (SELECT g_2
> .SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_2 WHERE (g_2.SYSID = 'DE29') AND (g_2.NEXTREC IN (SELECT g_3.SCOPEID FR
> OM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_3 WHERE (g_3.SYSID = 'DE29') AND (g_3.NEXTREC IN (SELECT g_4.SCOPEID FROM SECURITY
> _CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_4 WHERE (g_4.SYSID = 'DE29') AND (g_4.NEXTREC = 'CHRDEPT1'))))))))) OR (g_0.AUTHID IN (SELECT
> g_5.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_5 WHERE (g_5.SYSID = 'DE29') AND (g_5.NEXTREC IN (SELECT g_6.SCOPEI
> D FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_6 WHERE (g_6.SYSID = 'DE29') AND (g_6.NEXTREC IN (SELECT g_7.SCOPEID FROM SECU
> RITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_7 WHERE (g_7.SYSID = 'DE29') AND (g_7.NEXTREC = 'CHRDEPT1'))))))) OR (g_0.AUTHID IN (SELE
> CT g_8.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_8 WHERE (g_8.SYSID = 'DE29') AND (g_8.NEXTREC IN (SELECT g_9.SCOP
> EID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_9 WHERE (g_9.SYSID = 'DE29') AND (g_9.NEXTREC = 'CHRDEPT1'))))) OR (g_0.AUTH
> ID IN (SELECT g_10.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_10 WHERE (g_10.SYSID = 'DE29') AND (g_10.NEXTREC = 'C
> HRDEPT1'))) OR (g_0.AUTHID = 'CHRDEPT1'))
> The view definitions are shown below:
> <view name="SCPNEXT">
> <columns>
> <column name="sysid" type="varchar"/>
> <column name="scopeid" type="varchar"/>
> <column name="nextrec" type="varchar"/>
> </columns>
> <definition>
> #if ($db.count("select count(*) from sys.tables where Name='config' and SchemaName = 'security_db'") > 0)
> #set ($count = 0)
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> #if ($db.count("select count(*) from sys.tables where SchemaName = 'SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}'") == 0)
> #set ($count = $count + 1)
> #end
> #end
> #if ($count == 0)
> SELECT t.sysid, t.scopeid, t.nextrec
> FROM (
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> SELECT n.sysid, n.scopeid, n.nextrec
> FROM SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}.SCPNEXT n
> #if( $velocityHasNext ) UNION #end
> #end
> ) AS t
> #end
> #end
> </definition>
> </view>
> <view name="SCPXREF">
> <columns>
> <column name="sysid" type="varchar"/>
> <column name="authid" type="varchar"/>
> <column name="scopeid" type="varchar"/>
> <column name="authtype" type="varchar"/>
> </columns>
> <definition>
> #if ($db.count("select count(*) from sys.tables where Name='config' and SchemaName = 'security_db'") > 0)
> #set ($count = 0)
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> #if ($db.count("select count(*) from sys.tables where SchemaName = 'SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}'") == 0)
> #set ($count = $count + 1)
> #end
> #end
> #if ($count == 0)
> SELECT sysid, scopeid, authid, authtype
> FROM (
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> SELECT x.sysid, x.scopeid, x.authid, x.authtype
> FROM SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}.SCPXREF x
> #if( $velocityHasNext ) UNION #end
> #end
> ) AS t
> #end
> #end
> </definition>
> </view>
> I guess the best way to test this is to define these views and run the input query with SHOWPLAN=DEBUG and see if the AUTHID substitution is occurring.
> Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 weeks, 4 days
[JBoss JIRA] (TEIID-5861) Salesforce translator should support nested joins
by Renat Eskenin (Jira)
[ https://issues.redhat.com/browse/TEIID-5861?page=com.atlassian.jira.plugi... ]
Renat Eskenin edited comment on TEIID-5861 at 5/31/20 5:15 AM:
---------------------------------------------------------------
I investigated bugs in some my tasks and described its with code of teiid engine (concrete strings in code of engine and how you can repair bug), but implementing of new functions is very difficult.
was (Author: i3draven):
I investigated bugs in some my tasks and described its with code, but implementing of new functions is very difficult.
> Salesforce translator should support nested joins
> -------------------------------------------------
>
> Key: TEIID-5861
> URL: https://issues.redhat.com/browse/TEIID-5861
> Project: Teiid
> Issue Type: Enhancement
> Components: Salesforce Connector
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: Backlog
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> For this SQL we have wrong generated SOQL
> {code}
> select
> price.Id,
> price.IsActive__c,
> price.name,
> price.PriceBook__c,
> book.DefaultCurrency__c,
> price.Price__c,
> price.ProductCode__c,
> price.ProductName__c,
> price.Product__c,
> product.Id,
> product.Name,
> product.Description
> from
> MSRP__c as price
> left outer join /*+ MAKEDEP */ Product2 as product on
> price.Product__c = product.id
> left outer join /*+ MAKEDEP */ Pricebook2 as book on
> price.PriceBook__c = book.id
> where
> price.PriceBook__c =:priceBookId
> and ProductCode__c in(
> :productCodes
> )
> and IsActive__c = true"
> {code}
> {code}
> START DATA SRC COMMAND: startTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=3 executionID=2 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sql=SELECT sf.Pricebook2.DefaultCurrency__c FROM sf.Pricebook2 WHERE sf.Pricebook2.Id = 'xxxxx'
> [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.COMMAND_LOG.SOURCE [Worker0_QueryProcessorQueue1]: SOURCE SRC COMMAND: endTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=2 executionID=1 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sourceCommand=[SELECT MSRP__c.Id, MSRP__c.IsActive__c, MSRP__c.Name, MSRP__c.PriceBook__c, MSRP__c.Price__c, MSRP__c.ProductCode__c, MSRP__c.ProductName__c, MSRP__c.Product__c, Product__r.Id, Product__r.Name, Product__r.Description FROM MSRP__c WHERE (MSRP__c.PriceBook__c = 'xxxx') AND ((MSRP__c.ProductCode__c IN(xxxxx)) AND (MSRP__c.IsActive__c = true))]
> [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.CONNECTOR [Worker1_QueryProcessorQueue2]: salesforce.9MPiB/GOwB5f.9MPiB/GOwB5f.0.3: Incoming Query: SELECT Pricebook2.DefaultCurrency__c FROM Pricebook2 WHERE Pricebook2.Id = 'xxxx'
> [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.COMMAND_LOG.SOURCE [Worker1_QueryProcessorQueue2]: SOURCE SRC COMMAND: endTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=3 executionID=2 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sourceCommand=[Using retrieve: Pricebook2.DefaultCurrency__c Pricebook2 [xxxx]]
> {code}
> But need to generate one. Because we have two relations in MSRP__c
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5962) Teiid locks many threads when Salesforce is disconnected
by Renat Eskenin (Jira)
Renat Eskenin created TEIID-5962:
------------------------------------
Summary: Teiid locks many threads when Salesforce is disconnected
Key: TEIID-5962
URL: https://issues.redhat.com/browse/TEIID-5962
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 12.3.1
Reporter: Renat Eskenin
Assignee: Steven Hawkins
Attachments: Снимок экрана от 2020-05-31 11-09-10.png
We had two incidents in our experimental service with teiid spring boot app. When Salesforce is down to 20min and service with teiid trying to call SQL from Salesforce we have many threads in tomcat server (in spring boot app). Then when 200 threads is activated service do not reply to requests because is "max threads" in tomcat of service.
Why teiid do not send response as "Salesforce is down - error" or connection timeout?
Micro schema:
HTTP Requests to REST api -> Teiid spring boot app -> {broken 20min}Salesforce
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5861) Salesforce translator should support nested joins
by Renat Eskenin (Jira)
[ https://issues.redhat.com/browse/TEIID-5861?page=com.atlassian.jira.plugi... ]
Renat Eskenin commented on TEIID-5861:
--------------------------------------
I investigated bugs in some my tasks and described its with code, but implementing of new functions is very difficult.
> Salesforce translator should support nested joins
> -------------------------------------------------
>
> Key: TEIID-5861
> URL: https://issues.redhat.com/browse/TEIID-5861
> Project: Teiid
> Issue Type: Enhancement
> Components: Salesforce Connector
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: Backlog
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> For this SQL we have wrong generated SOQL
> {code}
> select
> price.Id,
> price.IsActive__c,
> price.name,
> price.PriceBook__c,
> book.DefaultCurrency__c,
> price.Price__c,
> price.ProductCode__c,
> price.ProductName__c,
> price.Product__c,
> product.Id,
> product.Name,
> product.Description
> from
> MSRP__c as price
> left outer join /*+ MAKEDEP */ Product2 as product on
> price.Product__c = product.id
> left outer join /*+ MAKEDEP */ Pricebook2 as book on
> price.PriceBook__c = book.id
> where
> price.PriceBook__c =:priceBookId
> and ProductCode__c in(
> :productCodes
> )
> and IsActive__c = true"
> {code}
> {code}
> START DATA SRC COMMAND: startTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=3 executionID=2 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sql=SELECT sf.Pricebook2.DefaultCurrency__c FROM sf.Pricebook2 WHERE sf.Pricebook2.Id = 'xxxxx'
> [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.COMMAND_LOG.SOURCE [Worker0_QueryProcessorQueue1]: SOURCE SRC COMMAND: endTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=2 executionID=1 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sourceCommand=[SELECT MSRP__c.Id, MSRP__c.IsActive__c, MSRP__c.Name, MSRP__c.PriceBook__c, MSRP__c.Price__c, MSRP__c.ProductCode__c, MSRP__c.ProductName__c, MSRP__c.Product__c, Product__r.Id, Product__r.Name, Product__r.Description FROM MSRP__c WHERE (MSRP__c.PriceBook__c = 'xxxx') AND ((MSRP__c.ProductCode__c IN(xxxxx)) AND (MSRP__c.IsActive__c = true))]
> [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.CONNECTOR [Worker1_QueryProcessorQueue2]: salesforce.9MPiB/GOwB5f.9MPiB/GOwB5f.0.3: Incoming Query: SELECT Pricebook2.DefaultCurrency__c FROM Pricebook2 WHERE Pricebook2.Id = 'xxxx'
> [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.COMMAND_LOG.SOURCE [Worker1_QueryProcessorQueue2]: SOURCE SRC COMMAND: endTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=3 executionID=2 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sourceCommand=[Using retrieve: Pricebook2.DefaultCurrency__c Pricebook2 [xxxx]]
> {code}
> But need to generate one. Because we have two relations in MSRP__c
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5960) Setting connection url property for MYSQL XA Datasource
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIID-5960?page=com.atlassian.jira.plugi... ]
Ramesh Reddy commented on TEIID-5960:
-------------------------------------
Teiid does not control any properties what is being set, if the MySQL data source supports the URL property on it then you can use it, if not no. AFAIK, I only seen Oracle supports the URL property on their data source. If MySQL also supports that is fine. Check the "setter" methods on the data source class then use them to define it.
> Setting connection url property for MYSQL XA Datasource
> -------------------------------------------------------
>
> Key: TEIID-5960
> URL: https://issues.redhat.com/browse/TEIID-5960
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi, JDBC Connector
> Affects Versions: 11.1.2
> Reporter: Manoj Majumdar
> Assignee: Steven Hawkins
> Priority: Minor
> Labels: Mysql-connector, teiid, xa-datasource-property
>
> I am trying to create a mysql xa datasource, but am unable to mention connection url properties in it. I have used property names such as "URL" and "connection-url", but the property is not visible in datasource.
> Also when I explicitly make a property tag in datasource for the url, it is working, but not when I am creating it through Admin Api,
> I need the connection url for setting mysql connection arguments such as "rewriteBatchedStatements=true"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5961) create foreign data wrapper statement cleanups
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5961?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5961:
---------------------------------------
[~rareddy] this is optional. It just makes it clearer for migrated vdbs and new ddl where the fdw options are supposed to go.
> create foreign data wrapper statement cleanups
> ----------------------------------------------
>
> Key: TEIID-5961
> URL: https://issues.redhat.com/browse/TEIID-5961
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 2 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> ConvertVDB is still adding create foreign data wrapper x; statements. These are not needed and should be suppressed. It's also causing some confusion that a user can enter
> create foreign data wrapper x options (...);
> The options are actually ignored. We should probably throw an exception instead. Either a type or a handler are required (we don't currently support a separate notion of a handler - it's treated the same as type).
> See also TEIID-5850
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5961) create foreign data wrapper statement cleanups
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5961?focusedWorklogId=12451177&pag... ]
Steven Hawkins logged work on TEIID-5961:
-----------------------------------------
Author: Steven Hawkins
Created on: 29/May/20 12:58 PM
Start Date: 29/May/20 12:58 PM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 2 hours)
Time Spent: 2 hours
Worklog Id: (was: 12451177)
> create foreign data wrapper statement cleanups
> ----------------------------------------------
>
> Key: TEIID-5961
> URL: https://issues.redhat.com/browse/TEIID-5961
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 2 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> ConvertVDB is still adding create foreign data wrapper x; statements. These are not needed and should be suppressed. It's also causing some confusion that a user can enter
> create foreign data wrapper x options (...);
> The options are actually ignored. We should probably throw an exception instead. Either a type or a handler are required (we don't currently support a separate notion of a handler - it's treated the same as type).
> See also TEIID-5850
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5961) create foreign data wrapper statement cleanups
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5961?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5961.
-----------------------------------
Resolution: Done
Updated the parser and the convert vdb routine as described.
> create foreign data wrapper statement cleanups
> ----------------------------------------------
>
> Key: TEIID-5961
> URL: https://issues.redhat.com/browse/TEIID-5961
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> ConvertVDB is still adding create foreign data wrapper x; statements. These are not needed and should be suppressed. It's also causing some confusion that a user can enter
> create foreign data wrapper x options (...);
> The options are actually ignored. We should probably throw an exception instead. Either a type or a handler are required (we don't currently support a separate notion of a handler - it's treated the same as type).
> See also TEIID-5850
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5961) create foreign data wrapper statement cleanups
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5961?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5961:
----------------------------------
Description:
ConvertVDB is still adding create foreign data wrapper x; statements. These are not needed and should be suppressed. It's also causing some confusion that a user can enter
create foreign data wrapper x options (...);
The options are actually ignored. We should probably throw an exception instead. Either a type or a handler are required (we don't currently support a separate notion of a handler - it's treated the same as type).
See also TEIID-5850
was:
ConvertVDB is still adding create foreign data wrapper x; statements. These are not needed and should be suppressed. It's also causing some confusion that a user can enter
create foreign data wrapper x options (...);
The options are actually ignored. We should probably throw an exception instead. Either a type or a handler are required (we don't currently support the notion of a handler).
See also TEIID-5850
Summary: create foreign data wrapper statement cleanups (was: create foreign data wrapper statements)
> create foreign data wrapper statement cleanups
> ----------------------------------------------
>
> Key: TEIID-5961
> URL: https://issues.redhat.com/browse/TEIID-5961
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> ConvertVDB is still adding create foreign data wrapper x; statements. These are not needed and should be suppressed. It's also causing some confusion that a user can enter
> create foreign data wrapper x options (...);
> The options are actually ignored. We should probably throw an exception instead. Either a type or a handler are required (we don't currently support a separate notion of a handler - it's treated the same as type).
> See also TEIID-5850
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months