[ 
https://issues.apache.org/jira/browse/CARBONDATA-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292055#comment-16292055
 ] 

Geetika Gupta commented on CARBONDATA-1748:
-------------------------------------------

I have tried the same on opensource spark and it follows the same behavior. So 
this JIRA would be invalid

> Carbon1.3.0- DB creation external path : Permission of created table and 
> database folder in carbon store not correct
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-1748
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-1748
>             Project: CarbonData
>          Issue Type: Bug
>          Components: other
>    Affects Versions: 1.3.0
>         Environment: 3 node ant cluster
>            Reporter: Chetan Bhat
>              Labels: security
>
> Steps : 
> In spark Beeline user executes the following queries.
> drop database if exists test_db1 cascade;
> create database test_db1 location 'hdfs://hacluster/user/test1';
> use test_db1;
> create table if not exists ORDERS(O_ORDERDATE string,O_ORDERPRIORITY 
> string,O_ORDERSTATUS string,O_ORDERKEY string,O_CUSTKEY string,O_TOTALPRICE 
> double,O_CLERK string,O_SHIPPRIORITY int,O_COMMENT string) STORED BY 
> 'org.apache.carbondata.format'TBLPROPERTIES ('table_blocksize'='128');
> User checks the permission of the created database and table in carbon store 
> using the  bin/hadoop fs -getfacl command.
> Issue : The Permission of created table and database folder in carbon store 
> not correct. i.e 
> # file: /user/test1/orders
> # owner: anonymous
> # group: users
> user::rwx
> group::r-x
> other::r-x
> Expected : Correct permissions for the created table and database folder in 
> carbon store should be 
> # file: /user/test1/orders
> # owner: anonymous
> # group: users
> user::rwx
> group::---
> other::---



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to