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 2018/07/09 08:42:00 UTC
[jira] [Resolved] (CARBONDATA-2642) Introduce configurable Lock
Path
[ https://issues.apache.org/jira/browse/CARBONDATA-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Venkata Ramana G resolved CARBONDATA-2642.
------------------------------------------
Resolution: Fixed
Fix Version/s: 1.4.1
> Introduce configurable Lock Path
> --------------------------------
>
> Key: CARBONDATA-2642
> URL: https://issues.apache.org/jira/browse/CARBONDATA-2642
> Project: CarbonData
> Issue Type: Improvement
> Reporter: Kunal Kapoor
> Assignee: Kunal Kapoor
> Priority: Minor
> Fix For: 1.4.1
>
> Time Spent: 12h 50m
> Remaining Estimate: 0h
>
> Currently table level lock files are prepared in table path and system level locks are created inside store.
> When supporting S3, locking cannot be done is using S3 files as S3 support only eventual consistency.
> So user can chose different HDFS location to configure locks, so that data can be on S3 and locks can be on HDFS.
> User also chose Zookeeper Lock if does not have HDFS location.
> So require to support a configuration path "carbon.lock.path"
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)