[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:all-tabpanel ]

Steven Hawkins resolved TEIID-5561.
-----------------------------------
    Resolution: Done


Where things stand:

- schema names will no longer collide with built-in aliases
- schema / vdb names will be decoded.  non-letter character letters are allowed by the our odata filter logic - which at least for the schema name is against the spec.
- we'll log a detail message when a table / procedure / column etc. name is not valid wrt odata.  The metadata will still be constructed as per usual, but the object in question won't be queryable.
- there was some clean-up of unused methods, and logic around names to start to add more consistency.

> 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)