[ https://issues.jboss.org/browse/TEIID-3401?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3401: --------------------------------------- The order by behavior will vary by translator. For most the expectation is that the engine will use aliases in the select clause, which will then be referenced in the order by. The web service translator? The ws translator only supports procedures. Ideally you'd first seem at what layer an issue is occurring. From the top down with the odata path you have: Odata URL -> Teiid SQL query (odata layer) Teiid SQL query planning -> processor plan (engine) Pushdown query -> source specific query (translator) With logging you should be able to see when things become invalid. With debugging, you can see the OData layer issue queries in org.teiid.odata.LocalClient. Then see the pushdown queries in org.teiid.dqp.internal.datamgr.DataManagerImpl.registerRequest, then see the source specific in whatever translator you are using. -- This message was sent by Atlassian JIRA (v6.3.11#6341)