[jira] [Resolved] (CARBONDATA-4107) MV Performance and Lock issues

["Akash R Nilugal (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CARBONDATA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Akash R Nilugal resolved CARBONDATA-4107.
-----------------------------------------
    Fix Version/s: 2.2.0
       Resolution: Fixed

> MV Performance and Lock issues
> ------------------------------
>
>                 Key: CARBONDATA-4107
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-4107
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Indhumathi Muthu Murugesh
>            Priority: Major
>             Fix For: 2.2.0
>
>          Time Spent: 11.5h
>  Remaining Estimate: 0h
>
> # After MV support multi-tenancy PR, mv system folder is moved to database level. Hence, during each operation, insert/Load/IUD/show mv/query, we are listing all the databases in the system and collecting mv schemas and checking if there is any mv mapped to the table or not. This will degrade performance of the query, to collect mv schemas from all databases, even though the table has mv or not.
>  # When different jvm process call touchMDTFile method, file creation and deletion can happen same time. This may fail the operation.



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