[
https://issues.jboss.org/browse/TEIID-2994?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2994:
---------------------------------------
Backwards compatibility can be achieved only if a NS is provided on
the SF OPTIONS() key values, just like any other.
Ramesh means backwards compatibility from a runtime perspective where namespaces was not
previously used. The answer there is yes, the logic already supports checking for
qualified and unqualified property keys.
From the example comparison, I don't see the translator using
supportsDelete, etc. Only "Supports Query" and "Supports Retrieve"
DDL Option properties not namespaced for salesforce
---------------------------------------------------
Key: TEIID-2994
URL:
https://issues.jboss.org/browse/TEIID-2994
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 8.7
Reporter: Mark Drilling
Assignee: Ramesh Reddy
Attachments: DDLExtOptionsComparison.txt
The Option keys for DDL with saleforce source are not getting namespaced. This is
inconsistent with other sources like excel. See attached file - comparison of two tables
- Excel source vs Salesforce source. The excel keys are prefixed with a namespace
teiid_excel: but the salesforce keys are not.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)