You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2015/11/18 17:21:11 UTC

[jira] [Commented] (FALCON-1308) Allow namespace-ing of custom properties in the entity specification

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

Ajay Yadava commented on FALCON-1308:
-------------------------------------

The work in FALCON-1434 added the ability to specify properties for the purpose of enabling scheduler selection. FALCON-1573 has extended it to submit custom properties that will be visible in Oozie Workflows. With properties being introduced from both user and falcon there is a renewed requirement for adding namespaces to distinguish between the two. With FALCON-1573 about to be committed, to avoid backward incompatibility reasons we should do it as part of the same release as FALCON-1573.

> Allow namespace-ing of custom properties in the entity specification
> --------------------------------------------------------------------
>
>                 Key: FALCON-1308
>                 URL: https://issues.apache.org/jira/browse/FALCON-1308
>             Project: Falcon
>          Issue Type: Improvement
>          Components: common
>            Reporter: Pallavi Rao
>
> There are some Falcon system properties that are supplied as custom properties in the Entity definition. Ideally, we should prefix these with "falcon.system" to distinguish them from user-supplied properties.
> Currently, we cannot have property names that have '.' in them as the Commons CLI (OptionValidator) rejects such names.



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