You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@carbondata.apache.org by "Venkata Ramana G (JIRA)" <ji...@apache.org> on 2017/04/20 15:20:04 UTC

[jira] [Resolved] (CARBONDATA-925) CarbonEnv is static & shared among all the Sessions. Cached relation in 1 session is not getting refreshed when another session is adding/dropping column

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

Venkata Ramana G resolved CARBONDATA-925.
-----------------------------------------
       Resolution: Fixed
         Assignee: Naresh P R
    Fix Version/s: 1.1.0-incubating

> CarbonEnv is static & shared among all the Sessions. Cached relation in 1 session is not getting refreshed when another session is adding/dropping column
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-925
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-925
>             Project: CarbonData
>          Issue Type: Bug
>         Environment: Spark 2.1
>            Reporter: Naresh P R
>            Assignee: Naresh P R
>             Fix For: 1.1.0-incubating
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> WIth multiple beeline connects in single thriftserver, CarbonEnv object is static. When user performs alter operation in 1 beeline, latest updated schema information is not reflecting 2nd beeline.
> Assume following concurrent operations
> 1) Beeline => select query on table1 (CarbonDatasourceRelation is cached)
> 2) spark-sql => add new column on table1 (this will refresh carbonMetastore available in carbonenv)
> 3) Beeline => Select query on table1 (This operation fails because it does not know whether the carbonMetastore is refreshed, hence cached CarbonDatasourceRelation will be returned which will not have newly added columns in schema fields)
> Corrected this problem by changing CarbonEnv Object to class which will be instantiated for each Session



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)