[teiid-issues] [JBoss JIRA] (TEIID-5561) Prevent alias collisions with built-in odata schema

[Steven Hawkins (Jira)]

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

Steven Hawkins commented on TEIID-5561:
---------------------------------------

Thanks.  Forgot to check the ABNF.  That clarifies what is expected.  Using the referenced TSimpleIdentifier pattern confirms that most non-letter characters are not accepted.  That is a problem for us in that it's much more restrictive than SQL identifiers.  The olingo metadata layer does not apply any restrictions, so we can create invalid metadata that is not queryable.  It is possible to choose a naming replacement strategy similar to what is done with sql/xml names, but that will be a big change at first glance given our assumptions about the 1-1 mapping between odata and teiid metadata 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)