[teiid-issues] [JBoss JIRA] (TEIID-5833) Update extension metadata uri's

[Steven Hawkins (Jira)]

    [ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804583#comment-13804583 ] 

Steven Hawkins commented on TEIID-5833:
---------------------------------------

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.

> Update extension metadata uri's
> -------------------------------
>
>                 Key: TEIID-5833
>                 URL: https://issues.jboss.org/browse/TEIID-5833
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Major
>             Fix For: 13.0
>
>
> There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer.  We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes.  
> The only issue with changes is when the extension properties are left fully qualified in the metadata.  We'd need to lookup under both the old and new versions.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)