falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karishma Gulati (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FALCON-497) Able to submit feed even though owner of storage specified (location type=data) is different from the ACL owner
Date Wed, 25 Jun 2014 13:20:24 GMT
Karishma Gulati created FALCON-497:

             Summary: Able to submit feed even though owner of storage specified (location
type=data) is different from the ACL owner
                 Key: FALCON-497
                 URL: https://issues.apache.org/jira/browse/FALCON-497
             Project: Falcon
          Issue Type: Bug
          Components: general
    Affects Versions: 0.6
         Environment: QA
            Reporter: Karishma Gulati

<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="uri:falcon:feed:0.1" name="raaw-logs16-784f11fb-0952-4b0e-ae17-a767f094068a"
description="clicks log">
    <partition name="country"/>
    <partition name="colo"/>
  <late-arrival cut-off="hours(6)"/>
    <cluster name="corp-456c8ba1-00d9-46d2-a9c1-f5e0a561f8cc" type="source">
      <validity start="2009-02-01T00:00Z" end="2099-05-01T00:00Z"/>
      <retention limit="months(9000)" action="delete"/>
    <location type="data" path="/samarth/input-data/rawLogs/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}"/>
    <location type="stats" path="/projects/ivory/clicksStats"/>
    <location type="meta" path="/projects/ivory/clicksMetaData"/>
  <ACL owner="karishma" group="group" permission="0x755"/>
  <schema location="/schema/clicks" provider="protobuf"/>
    <property name="field1" value="value1"/>
    <property name="field2" value="value2"/>

If location path (type=data) exists in hdfs, I'm succesfully able to submit the feed, even
with an ACL owner different from the storage owner.

In falcon, the owner of the entire path 
<location type="data" path="/samarth/input-data/rawLogs/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}"/>
(including the variables) is being checked for, instead of just that of "/samarth/input-data/rawLogs/".

The feature successfully works if the location paths (type=meta or type=stats) exist on hdfs,
and the owner of these is different from the ACL owner.In that case, I'm not allowed to submit
the feed, and get the following error: 

 <?xml version="1.0" encoding="UTF-8"?>
  <message>ua1/Can't validate storage ACL (URI hdfs:// ACL owner
karishma doesn't match the actual file owner dataqa</message>

This message was sent by Atlassian JIRA

View raw message