[jira] [Commented] (CARBONDATA-4025) storage space for MV is double to that of a table on which MV has been created.

[Akash R Nilugal (Jira)]

    [ https://issues.apache.org/jira/browse/CARBONDATA-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218159#comment-17218159 ]

Akash R Nilugal commented on CARBONDATA-4025:
---------------------------------------------

Hi,

MV stores the aggregated data, so how the number of rows are same in MV also?

can you give further details like, test queries, which granularity u tried? It would help to find the problem if any or suggest the proper way.

Also, please join and discuss in slack channel, as jira wont be notified to all.

https://join.slack.com/t/carbondataworkspace/shared_invite/zt-g8sv1g92-pr3GTvjrW5H9DVvNl6H2dg

Thanks

> storage space for MV is double to that of a table on which MV has been created.
> -------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-4025
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-4025
>             Project: CarbonData
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.0.1
>         Environment: Apcahe carbondata 2.0.1
> Apache spark 2.4.5
> Hadoop 2.7.2
>            Reporter: suyash yadav
>            Priority: Major
>
> We are doing a POC based on carbondata but we have observed that when we create n MV on a table with timeseries function of same granualarity the MV takes double the space of the table.
>  
> In my scenario, My table has 1.3 million records and MV also has same number of records but the size of the table is 3.6 MB but the size of the MV is around 6.5 MB.
> This is really important for us as critical business decision are getting affected due to this behaviour.

--
This message was sent by Atlassian Jira
(v8.3.4#803005)