[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5833 at 10/25/19 2:30 PM: ----------------------------------------------------------------- In more detail: * "set namespace" will throw an exception. Anyone using a custom namespace will need to choose a consistent name/prefix across all usage. The fix in most cases is just to remove the set namespace statement and replace the prefix usage with the uri. If they choose to go with something other than the uri, then that may require changes in custom translators and other sql. * deprecate AbstractMetadataRecord.getProperty(String key, boolean checkUnqualified). The new getProperty will look for teiid_ properties by both prefix and fqn for backwards compatibility. * change all of our built-in lookups (mostly in translators) to just use the prefix name * sys.properties will report teiid_ properties by both the prefix and uri. was (Author: shawkins): In more detail: * * "set namespace" will throw an exception. Anyone using a custom namespace will need to choose a consistent name/prefix across all usage. The fix in most cases is just to remove the set namespace statement. * deprecate AbstractMetadataRecord.getProperty(String key, boolean checkUnqualified) * change all of our built-in lookups (mostly in translators) to just use the prefix name The only big breaking change is for custom translator development that were using uri fqn references to get properties. This will require a code change on their end. -- This message was sent by Atlassian Jira (v7.13.8#713008)