[
https://issues.jboss.org/browse/TEIID-4686?page=com.atlassian.jira.plugin...
]
Juraj Duráni commented on TEIID-4686:
-------------------------------------
The problem is not with ORDER BY in general. It happens only in combination with JOIN. Do
we want to disable support for ORDER BY in general? Isn't there way how to disable it
only after JOIN?
One more note. The correct condition in this case should be:
{code:java}
if(getVersion().compareTo(V_0_162) < 0){
...
}
{code}
PrestoDB translator - ordering of joined tables fails
-----------------------------------------------------
Key: TEIID-4686
URL:
https://issues.jboss.org/browse/TEIID-4686
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.8.6_3
Reporter: Juraj Duráni
Assignee: Kylin Soong
Fix For: 9.2.1
Issuing query like \[1\] causes an exception in PrestoDB. This seems to be PrestoDB
issue. I found similar issue \[2\], but that one should be fixed. I have created a new
issue \[3\]. Removing one column from ORDER BY, query returns correct result.
Not sure if we can do something about it without avoiding pushing JOIN.
I suggest either to fix this (if simple enough) or add a note to the documentation.
\[1\]
{code:sql}
SELECT a.intkey, b.intkey FROM BQT1.SmallA AS a INNER JOIN BQT1.SmallB AS b on a.intkey =
b.intkey ORDER BY 1, 2
{code}
\[2\]
https://github.com/prestodb/presto/issues/1621
\[3\]
https://github.com/prestodb/presto/issues/7010
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)