[jira] [Resolved] (CARBONDATA-3602) MV datamap is not being hit in different session and table not found error while creating datamap

[Akash R Nilugal (Jira)]

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

Kunal Kapoor resolved CARBONDATA-3602.
--------------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

> MV datamap is not being hit in different session and table not found error while creating datamap
> -------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-3602
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3602
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Akash R Nilugal
>            Assignee: Akash R Nilugal
>            Priority: Minor
>             Fix For: 2.0.0
>
>          Time Spent: 7h 10m
>  Remaining Estimate: 0h
>
> MV datamap is not being hit in different session and table not found error while creating datamap
> issue1:
> when query is being run from different sessions, datamap is not being hit and behaves inconsistently .
> issue2:
> 1. login to client like beeline
> 2. create database db1
> 3. create table t1
> 4. create datamap datamap1
> 5. log out of beeline
> 6.log in again
> 7. drop table db1.t1
> 8. create same table t1
> 9. create same datamap datamap1 on t1 in default database
> Exception is thrown as table t1 not found.

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