[ https://issues.jboss.org/browse/TEIID-2994?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-2994: ------------------------------------- We have the new capability (Designer 8.5) to discover the MEDs available through translator properties via the new Teiid API (Teiid 8.7) . These MED namespaces are defined in those properties. Our preferred way of doing things in the Teiid Connection importer is to match the NS in the DDL OPTIONS() to the NS in the MEDs. Not having any NS in those OPTIONS(), prevents us from doing so. Our only option would be to fall back on the Translator type during the import and select a hard-coded NS to match it and that seems like a hack/risky way to go. If there is no NS prefix in the OPTIONS() keys, then how is the DDL going to be tied to a specific Translator type? Backwards compatibility can be achieved only if a NS is provided on the SF OPTIONS() key values, just like any other. -- This message was sent by Atlassian JIRA (v6.2.3#6260)