[
https://issues.jboss.org/browse/TEIID-3142?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3142:
---------------------------------------
Presumably this and impala issue are due to the column/server having a different collation
than the expected ascii/utf. We don't yet have a great story for alternative
collations. Typically we simply defer to the source sorting characteristics, such as with
null first/last handling when not specified by the user query. The workarounds are to
change the collation on the source or to disable order by support at the translator.
Vanilla Hive sorting issue
--------------------------
Key: TEIID-3142
URL:
https://issues.jboss.org/browse/TEIID-3142
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 8.7.1
Reporter: Filip Nguyen
Assignee: Steven Hawkins
It seems that Vanilla Apache Hive 0.13 sorts in a yet another different way than what we
expect and also differently from Cloudera Imapla (another Hive flavor).
SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA order by BQT1.SmallA.StringNum
1: -1
2: -10
3: -11
4: -12
5: -13
6: -14
7: -15
8: -16
9: -17
10: -18
11: -19
12: -2
13: -20
14: -21
15: -22
16: -24
17: -3
18: -4
19: -5
20: -6
21: -8
22: -9
23: 0
24: 1
25: 10
26: 11
27: 12
28: 13
29: 14
30: 15
31: 16
32: 17
33: 18
34: 19
35: 2
36: 20
37: 21
38: 22
39: 23
40: 24
41: 3
42: 4
43: 5
44: 6
45: 7
46: 8
47: null
48: null
49: null
50: null
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)