You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by Pradeep Bhadani <pr...@bigdatapartnership.com> on 2015/06/19 10:49:42 UTC

Falcon staging directory 777 permissions?

Hi ,

Documentation here
http://falcon.apache.org/0.6-incubating/EntitySpecification.html explains
about staging directory in CLuster Entity and puts condition that  "
*staging* must have 777 permissions" .
Is this a hard condition or can we have permissions other than 777?
777 permission in not good when handling sensitive data.

Thanks,
Pradeep

-- 
 

*NOTICE AND DISCLAIMER*

This email (including attachments) is confidential. If you are not the 
intended recipient, notify the sender immediately, delete this email from 
your system and do not disclose or use for any purpose.

Business Address: Eagle House, 163 City Road, London, EC1V 1NR. United 
Kingdom
Registered Office: Finsgate, 5-7 Cranwood Street, London, EC1V 9EE. United 
Kingdom
Big Data Partnership Limited is a company registered in England & Wales 
with Company No 7904824

Re: Falcon staging directory 777 permissions?

Posted by Ajay Yadav <aj...@gmail.com>.
+user

On Fri, Jun 19, 2015 at 6:43 PM, Ajay Yadav <aj...@gmail.com> wrote:

> +users(for benefit of the users who are not on dev mailing list)
> Hi Pradeep,
>
> The staging directory stores only the feed/process definitions and job
> logs. It doesn't contain the "data" (which your process consume/produce)
> which is stored in the feed's locations. It is not required to have 777
> permission for the "data". Do you have a use case where staging directory
> contains sensitive information?
>
>
>
>
> On Fri, Jun 19, 2015 at 2:19 PM, Pradeep Bhadani <
> pradeep.bhadani@bigdatapartnership.com> wrote:
>
>> Hi ,
>>
>> Documentation here
>> http://falcon.apache.org/0.6-incubating/EntitySpecification.html explains
>> about staging directory in CLuster Entity and puts condition that  "
>> *staging* must have 777 permissions" .
>> Is this a hard condition or can we have permissions other than 777?
>> 777 permission in not good when handling sensitive data.
>>
>> Thanks,
>> Pradeep
>>
>> --
>>
>>
>> *NOTICE AND DISCLAIMER*
>>
>> This email (including attachments) is confidential. If you are not the
>> intended recipient, notify the sender immediately, delete this email from
>> your system and do not disclose or use for any purpose.
>>
>> Business Address: Eagle House, 163 City Road, London, EC1V 1NR. United
>> Kingdom
>> Registered Office: Finsgate, 5-7 Cranwood Street, London, EC1V 9EE. United
>> Kingdom
>> Big Data Partnership Limited is a company registered in England & Wales
>> with Company No 7904824
>>
>
>

Re: Falcon staging directory 777 permissions?

Posted by Ajay Yadav <aj...@gmail.com>.
+user

On Fri, Jun 19, 2015 at 6:43 PM, Ajay Yadav <aj...@gmail.com> wrote:

> +users(for benefit of the users who are not on dev mailing list)
> Hi Pradeep,
>
> The staging directory stores only the feed/process definitions and job
> logs. It doesn't contain the "data" (which your process consume/produce)
> which is stored in the feed's locations. It is not required to have 777
> permission for the "data". Do you have a use case where staging directory
> contains sensitive information?
>
>
>
>
> On Fri, Jun 19, 2015 at 2:19 PM, Pradeep Bhadani <
> pradeep.bhadani@bigdatapartnership.com> wrote:
>
>> Hi ,
>>
>> Documentation here
>> http://falcon.apache.org/0.6-incubating/EntitySpecification.html explains
>> about staging directory in CLuster Entity and puts condition that  "
>> *staging* must have 777 permissions" .
>> Is this a hard condition or can we have permissions other than 777?
>> 777 permission in not good when handling sensitive data.
>>
>> Thanks,
>> Pradeep
>>
>> --
>>
>>
>> *NOTICE AND DISCLAIMER*
>>
>> This email (including attachments) is confidential. If you are not the
>> intended recipient, notify the sender immediately, delete this email from
>> your system and do not disclose or use for any purpose.
>>
>> Business Address: Eagle House, 163 City Road, London, EC1V 1NR. United
>> Kingdom
>> Registered Office: Finsgate, 5-7 Cranwood Street, London, EC1V 9EE. United
>> Kingdom
>> Big Data Partnership Limited is a company registered in England & Wales
>> with Company No 7904824
>>
>
>

Re: Falcon staging directory 777 permissions?

Posted by Ajay Yadav <aj...@gmail.com>.
+users(for benefit of the users who are not on dev mailing list)
Hi Pradeep,

The staging directory stores only the feed/process definitions and job
logs. It doesn't contain the "data" (which your process consume/produce)
which is stored in the feed's locations. It is not required to have 777
permission for the "data". Do you have a use case where staging directory
contains sensitive information?




On Fri, Jun 19, 2015 at 2:19 PM, Pradeep Bhadani <
pradeep.bhadani@bigdatapartnership.com> wrote:

> Hi ,
>
> Documentation here
> http://falcon.apache.org/0.6-incubating/EntitySpecification.html explains
> about staging directory in CLuster Entity and puts condition that  "
> *staging* must have 777 permissions" .
> Is this a hard condition or can we have permissions other than 777?
> 777 permission in not good when handling sensitive data.
>
> Thanks,
> Pradeep
>
> --
>
>
> *NOTICE AND DISCLAIMER*
>
> This email (including attachments) is confidential. If you are not the
> intended recipient, notify the sender immediately, delete this email from
> your system and do not disclose or use for any purpose.
>
> Business Address: Eagle House, 163 City Road, London, EC1V 1NR. United
> Kingdom
> Registered Office: Finsgate, 5-7 Cranwood Street, London, EC1V 9EE. United
> Kingdom
> Big Data Partnership Limited is a company registered in England & Wales
> with Company No 7904824
>