[jira] [Resolved] (CARBONDATA-40) Make metastore_db location of derby configurable in CarbonContext

["Ravindra Pesala (JIRA)" <ji...@apache.org>]

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

Ravindra Pesala resolved CARBONDATA-40.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.1.0-incubating

> Make metastore_db location of derby configurable in CarbonContext
> -----------------------------------------------------------------
>
>                 Key: CARBONDATA-40
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-40
>             Project: CarbonData
>          Issue Type: Improvement
>            Reporter: Ravindra Pesala
>            Assignee: Ravindra Pesala
>             Fix For: 0.1.0-incubating
>
>
> Currently metastore_db location of derby is not configurable and it is always created in current directory. Because of this constraint user not able to create multiple CarbonContext with derby db. This is the reason user cannot create CarbonContext in spark-shell with standalone derby db.
> To overcome the above issue we can make the derby db location configurable while creating CarbonContext.
> Case 1:
> {code}
> val cc = new CarbonContext(sc)
> {code}
> In above scenario, default store location at `./carbondata` it means store is created in current directory.And default metastore location `./carbonmetastore`, it means metastore is created at current directory.
> Case 2 :
> {code}
> val cc = new CarbonContext(sc, storeLocation)
> {code}
> In above scenario, default metastore location `./carbonmetastore`, it means metastore is created at current directory.
> Case 3: 
> {code}
> val cc = new CarbonContext(sc, storeLocation, metastoreLocation)
> {code}
> In above scenario all parameters are passed, so store location and metastoreLocation would be created at desired location.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)