Return-Path: 
 <dev-return-3203-apmail-falcon-dev-archive=falcon.apache.org@falcon.incubator.apache.org>
X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org
Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3670C10BC1
	for <apmail-falcon-dev-archive@minotaur.apache.org>;
 Tue, 11 Mar 2014 11:23:15 +0000 (UTC)
Received: (qmail 92278 invoked by uid 500); 11 Mar 2014 11:23:14 -0000
Delivered-To: apmail-falcon-dev-archive@falcon.apache.org
Received: (qmail 92144 invoked by uid 500); 11 Mar 2014 11:23:12 -0000
Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@falcon.incubator.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@falcon.incubator.apache.org>
List-Post: <mailto:dev@falcon.incubator.apache.org>
List-Id: <dev.falcon.incubator.apache.org>
Reply-To: dev@falcon.incubator.apache.org
Delivered-To: mailing list dev@falcon.incubator.apache.org
Received: (qmail 92103 invoked by uid 99); 11 Mar 2014 11:23:07 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 11:23:07 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Tue, 11 Mar 2014 11:23:05 +0000
Received: (qmail 91411 invoked by uid 99); 11 Mar 2014 11:22:45 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 11:22:45 +0000
Date: Tue, 11 Mar 2014 11:22:45 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12700677.1394536879621.42810.1394536965155@arcas>
In-Reply-To: <JIRA.12700677.1394536879621@arcas>
References: <JIRA.12700677.1394536879621@arcas>
Subject: [jira] [Updated] (FALCON-346) Feed can't be submitted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/FALCON-346?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 updated FALCON-346:
----------------------------------------

    Affects Version/s: 0.5

> Feed can't be submitted
> -----------------------
>
>                 Key: FALCON-346
>                 URL: https://issues.apache.org/jira/browse/FALCON-346
>             Project: Falcon
>          Issue Type: Bug
>          Components: feed
>    Affects Versions: 0.5
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>
> With the latest build on master, I submitted the following cluster:
> {code}
> <cluster colo=3D"local" description=3D"Local cluster" name=3D"local" xmln=
s=3D"uri:falcon:cluster:0.1">
>     <interfaces>
>         <interface type=3D"readonly" endpoint=3D"hftp://localhost:50010" =
version=3D"1.1.2"/>
>         <interface type=3D"write" endpoint=3D"hdfs://localhost:8020" vers=
ion=3D"1.1.2"/>
>         <interface type=3D"execute" endpoint=3D"localhost:8021" version=
=3D"1.1.2"/>
>         <interface type=3D"workflow" endpoint=3D"http://localhost:11000/o=
ozie/" version=3D"4.0.0"/>
>         <interface type=3D"messaging" endpoint=3D"tcp://localhost:61616" =
 version=3D"5.7.0"/>
>     </interfaces>
>     <locations>
>         <location name=3D"staging" path=3D"/falcon/staging"/>
>         <location name=3D"temp" path=3D"/falcon/tmp"/>
>         <location name=3D"working" path=3D"/falcon/working"/>
>     </locations>
>     <properties>
>     </properties>
> </cluster>
> {code}
> with:
> {code}
> bin/falcon entity -submit -type cluster -file local.xml
> {code}
> The submit is OK, and I can see the cluster in the Falcon configuration s=
tore:
> {code}
> bin/falcon entity -list -type cluster
> (cluster) local(null)
> {code}
> Now, I create the following feed:
> {code}
> <feed description=3D"" name=3D"output" xmlns=3D"uri:falcon:feed:0.1">
>     <groups>output</groups>
>     <frequency>minutes(10)</frequency>
>     <clusters>
>         <cluster name=3D"local">
>             <validity start=3D"2012-07-20T03:00Z" end=3D"2099-07-16T00:00=
Z"/>
>             <retention limit=3D"hours(10)" action=3D"delete"/>
>         </cluster>
>     </clusters>
>     <locations>
>         <location type=3D"data" path=3D"/data/output"/>
>     </locations>
>  =20
>     <ACL owner=3D"jbonofre" group=3D"supergroup" permission=3D"0x644"/>
>     <schema location=3D"none" provider=3D"none"/>
> </feed>
> {code}
> However, when I try to submit this feed, I got:
> {code}
> bin/falcon entity -submit -type feed -file ~/demo/entity/output.xml=20
> Error: Cluster entity vertex must exist: local
> {code}
> whereas local cluster exists.
> It seems that it's a regression introduced in EntityRelationshipGraphBuil=
der.
> I gonna take a look on that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)