[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3553: ------------------------------------- Yes, the ambiguity only exists in V2, because in V2, the $metadata can define multiple "schema" objects, and entity containers and only one of them can be set as default. When the schema name is not available it can be run against the default one. But in Teiid's implementation we have no default entity container is set, so it required that user uses the fully qualified name to access the entities. In V4, there is only one schema and entity container for $metadata, but you can define references to other $metadata schemas in $metadata and use them with their fully qualified name in defining the relationships etc. I would categorize this as invalid usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)