[CARBONDATA-2528] MV Datamap - When the MV is created with the order by, then when we execute the corresponding query defined in MV with order by, then the data is not accessed from the MV.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.5.0, 1.4.1
• Component/s: data-query
• Labels: CarbonData MV Materialistic_Views
• Environment: 3 node Opensource ANT cluster. (Opensource Hadoop 2.7.2+ Opensource Spark 2.2.1+ Opensource Carbondata 1.3.1)
• Assignee: Ravindra Pesala
• Reporter: Prasanna Ravichandran
• Created: 24/May/18 14:39
• Updated: 01/Aug/18 11:28
• Resolved: 15/Jul/18 06:51

Description

When the MV is created with the order by condition, then when we execute the corresponding query defined in MV along with order by, then the data is not accessed from the MV. The data is being accessed from the maintable only. 

Test queries:

create datamap MV_order using 'mv' as select empno,sum(salary)+sum(utilization) as total from originTable group by empno order by empno;
create datamap MV_desc_order using 'mv' as select empno,sum(salary)+sum(utilization) as total from originTable group by empno order by empno DESC;
rebuild datamap MV_order;
rebuild datamap MV_desc_order;
explain select empno,sum(salary)+sum(utilization) as total from originTable group by empno order by empno;
explain select empno,sum(salary)+sum(utilization) as total from originTable group by empno order by empno DESC;

Expected result: MV with order by condition should access data from the MV table only.

 

Please see the attached document for more details.

Issue Links

• is a child of: CARBONDATA-2628 Fix MV defects
• links to: GitHub Pull Request #2453