[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4520: --------------------------------------- There are three scenarios: 1. the engine cares about the null order, which should only be if it is specified by the user query / view etc. - in which case the engine will consult with the source default to see if it matches. If not an explicit null sort option will be added - but only if the source supports it. If the source does not support explicit null ordering, then we'll inhibit the pushdown of the order by. 2. the engine doesn't care about the null order - in which case no explicit null order is sent down, the engine simply accepts whatever the source provides. 3. if the system property org.teiid.pushdownDefaultNullOrder is set the engine makes a best effort that won't inhibit the sort pushdown to enforce the engine's default sort order (low - but can be changed with org.teiid.defaultNullOrder) When testing sources that support an explicit null ordering it's best to org.teiid.pushdownDefaultNullOrder=true for maximal consistency. -- This message was sent by Atlassian JIRA (v7.5.0#75005)