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

SHREELEKHYA GAMPA updated CARBONDATA-3952:
------------------------------------------
    Description: 
After reset query not hitting MV.
With the reset, spark.sql.warehouse.dir and carbonStorePath don't match and the 
databaseLocation will change to old table path format. So, new tables that are 
created after reset, take a different path incase of default.

Closing this , as it is identified as spark bug. More details can be found at 
https://issues.apache.org/jira/browse/SPARK-31234

  was:
After reset query not hitting MV.
With the reset, spark.sql.warehouse.dir and carbonStorePath don't match and the 
databaseLocation will change to old table path format. So, new tables that are 
created after reset, take a different path incase of default.

Closing this PR, as it is identified as spark bug. More details can be found at 
https://issues.apache.org/jira/browse/SPARK-31234


> After reset query not hitting MV
> --------------------------------
>
>                 Key: CARBONDATA-3952
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3952
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: SHREELEKHYA GAMPA
>            Priority: Minor
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> After reset query not hitting MV.
> With the reset, spark.sql.warehouse.dir and carbonStorePath don't match and 
> the databaseLocation will change to old table path format. So, new tables 
> that are created after reset, take a different path incase of default.
> Closing this , as it is identified as spark bug. More details can be found at 
> https://issues.apache.org/jira/browse/SPARK-31234



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

Reply via email to