Bug 1329178 - Impala - result set is not sorted if ORDER BY is defined in query
Summary: Impala - result set is not sorted if ORDER BY is defined in query
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ER3
: 6.3.0
Assignee: Van Halbert
QA Contact: Filip Elias
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 10:35 UTC by Juraj Duráni
Modified: 2016-08-24 11:37 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:37:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4160 0 Blocker Closed Impala - result set is not sorted if ORDER BY is defined in query 2016-08-18 09:10:05 UTC

Description Juraj Duráni 2016-04-21 10:35:36 UTC
Query:
SELECT g_1.StringNum AS c_0 FROM Source.SmallA AS g_1 WHERE g_1.IntKey <= 50 UNION ALL SELECT g_0.StringNum AS c_0 FROM Source.SmallB AS g_0 WHERE g_0.IntKey > 50 ORDER BY c_0

Result: as you can see, nulls are not next to each other
|StringNum|
|-24|
|<null>|
|-14|
|-13|
|-12|
|-11|
|-10|
|-9|
|-8|
|<null>|
|-6
|-5|
|...|

Expected result: this is result of simple query SELECT stringnum FROM source.smalla ORDER BY 1
|StringNum|
|-1|
|-10|
|-11|
|-12|
|-13|
|-14|
|-15|
|...|

Comment 1 JBoss JIRA Server 2016-04-21 16:21:16 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-4160 to Resolved

Comment 2 Juraj Duráni 2016-04-25 05:48:22 UTC
Setting flag blocker? because related JIRA is a blocker.

Comment 3 JBoss JIRA Server 2016-06-03 20:34:40 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-4160 to Closed


Note You need to log in before you can comment on or make changes to this bug.