[teiid-issues] [JBoss JIRA] (TEIID-2994) DDL Option properties not namespaced for salesforce

[ https://issues.jboss.org/browse/TEIID-2994?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2994: ------------------------------------- yes, extension properties and translator go together for translator. That is why SteveH has been critical of design with namespaces as it is adding more issues than it is solving. I am not sure what you mean by here. Here is my concern, currently translator has for ages has been reading these properties without a namespace on the property name, if we add it now, if a user gets their old vdb and deploys into to new runtime, it will fail to recognize those values. However, there are couple things specific to this translator, * I am not sure why original author defined these metadata properties, but when I looked at them in the code they are being used at all. So it does not matter, so I could add the namespace * I could add compensating code to look both with name space and without thus I did not reject the issue, i will fix accordingly. Do we need this also in 8.7.1? -- This message was sent by Atlassian JIRA (v6.2.3#6260)