[ https://issues.redhat.com/browse/TEIIDSB-213?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-213: ---------------------------------------- I don't quite understand that conclusion yet. There may be some confusion here between the Teiid and source queries. In the no rows case you issued the Teiid query: "SELECT a.ArticleNumber,a.Id,a.KnowledgeArticleId,a.Language FROM Regular_Articles__kav a WHERE a.Language = 'it' LIMIT 5" There are no aliases used in the source query. In fact user level query aliasing is never used in the source SOQL by Teiid, it is only pushed to determine the proper form of self join queries and then discarded. That is not a problem, it is expected behavior. Again, you should not be looking at the Teiid query, but the source SOQL query that is being generated. That is not the SOQL, but the pushdown query from the query plan. The user query is converted to a query plan that contains pushdown queries you can see those in the processor plan or in the log as DATA SOURCE COMMAND to the relevant sources. Those pushdown queries are expressed in Teiid SQL. At runtime when those pushdown queries are processed it's the job of the translator to covert that into source SQL, DSL, API calls of whatever the source supports - in the log as SOURCE SRC COMMAND. In this case you can see logs similar to: [Worker0_QueryProcessorQueue0]: SOURCE SRC COMMAND: endTime=2020-06-26 17:42:07.505 requestID=Ecs7P/wl/YGs.0 sourceCommandID=0 executionID=0 txID=null modelName=salesforce translatorName=mysalesforce sessionID=Ecs7P/wl/YGs principal=anonymous sourceCommand=[SELECT Regular_Articles__kav.ArticleNumber, Regular_Articles__kav.Id, Regular_Articles__kav.KnowledgeArticleId, Regular_Articles__kav.Language FROM Regular_Articles__kav WHERE Regular_Articles__kav.Language = 'it' LIMIT 5] In other words it doesn't matter what quoting, aliases, etc. you have aliases in your user query the source SOQL will be the same. If you are getting an unexpected row count, I would suggest not using the limit and/or where predicate to see if you do get expected results otherwise. -- This message was sent by Atlassian Jira (v7.13.8#713008)