[teiid-issues] [JBoss JIRA] (TEIID-5561) Prevent alias collisions with built-in odata schema
Steven Hawkins (Jira)
issues at jboss.org
Wed Jan 16 16:28:02 EST 2019
[ https://issues.jboss.org/browse/TEIID-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683341#comment-13683341 ]
Steven Hawkins edited comment on TEIID-5561 at 1/16/19 4:25 PM:
----------------------------------------------------------------
URL reserved characters are a problem also. The odata filter uses non decoded string to determine the vdb, version, and schema. I can't really find a reference in the odata spec as to the expectation or limitation on schema names.
was (Author: shawkins):
URL reserved characters are a problem also. The odata filter uses httpRequest.getContextPath() to determine the vdb, version, and schema - but that url is not decoded. I can't really find a reference in the odata spec as to the expectation or limitation on schema names.
> Prevent alias collisions with built-in odata schema
> ---------------------------------------------------
>
> Key: TEIID-5561
> URL: https://issues.jboss.org/browse/TEIID-5561
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> It is problematic to have a Teiid model/schema with the name:
> olingo-extensions
> teiid
> edm
> as that will use an alias that conflicts with built-in handling. We should provide an error/warning as appropriate or come up with the logic to introduce a non-conflicting alias.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the teiid-issues
mailing list