falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Balu Vellanki (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FALCON-1657) <notification> tag is at different locations in feed and process xsd
Date Thu, 10 Dec 2015 02:28:11 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Balu Vellanki resolved FALCON-1657.
-----------------------------------
    Resolution: Invalid

I was looking at wrong .xsd files. This is not an issue. 

> <notification> tag is at different locations in feed and process xsd
> --------------------------------------------------------------------
>
>                 Key: FALCON-1657
>                 URL: https://issues.apache.org/jira/browse/FALCON-1657
>             Project: Falcon
>          Issue Type: Bug
>          Components: feed, process
>            Reporter: Balu Vellanki
>            Assignee: Balu Vellanki
>
> In Feed instance , notification tag should come right before ACL in the entity definition.
In sample entity, 
> {code}
> <feed description="clicks log" name="clicks" xmlns="uri:falcon:feed:0.1">
>     ...
>     </locations>
>     <notification type="email" to="falcon@localhost"/>
>     <ACL owner="testuser-ut-user" group="group" permission="0x755”/>
> ...
> </feed>
> {code}
> 2. Email notification tag should be last tag in the process entity. Sample xml is 
> {code}
> <process name="[process name]">
>     ...
>     <notification type="email" to="bob@xyz.com,tom@xyz.com"/>
> </process>
> {code}
> When users are creating entity xml definitions, this discrepancy becomes a usability
issue.  A user can accidentally create a process entity with notification tag before ACL tag,
submit it and get an error. 
> I recommend making it consistent by having notification be last tag for all schedulable
entities.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message