[
https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3134:
---------------------------------------
If you do not specify an explicit null ordering (such as your example query) and the
system property org.teiid.pushdownDefaultNullOrder is not set or false, then you will get
the default ordering of the source, which was determined previously to be nulls high. If
org.teiid.pushdownDefaultNullOrder is set to true, then you should see the Teiid default
null ordering which is nulls low.
If you specify an explicit null ordering in the user query "ORDER BY StringNum NULLS
FIRST asc", then you should always expect to see that ordering.
Impala sorting Issue
--------------------
Key: TEIID-3134
URL:
https://issues.jboss.org/browse/TEIID-3134
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.9
Attachments: server.log
String sorting of impala is inconsistent with our expectations:
Impala sorting
---------------------------
SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA
Results
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
Expected
---------------------------
While we expect sorting to be consistent with other sources:
1: 0
2: 1
3: -1
4: 10
5: -10
6: 11
7: -11
8: 12
9: -12
10: 13
11: -13
12: 14
13: -14
14: 15
15: -15
16: 16
17: -16
18: 17
19: -17
20: 18
21: -18
22: 19
23: -19
24: 2
25: -2
26: 20
27: -20
28: 21
29: -21
30: 22
31: -22
32: 23
33: 24
34: -24
35: 3
36: -3
37: 4
38: -4
39: 5
40: -5
41: 6
42: -6
43: 7
44: 8
45: -8
46: -9
47: null
48: null
49: null
50: null
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)