falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1308) Allow namespace-ing of custom properties in the entity specification
Date Wed, 18 Nov 2015 16:32:11 GMT

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

Ajay Yadava commented on FALCON-1308:

I am in favor of introducing namespaces but would like to propose slightly different namespaces.
{noformat}falcon.* for system properties and no namespace prefix for user-supplied properties.{noformat}

I find this convention concise and no namespace for user properties will ensure sort of backward
compatibility with older properties being defined.

> 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
>            Priority: Blocker
> 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

View raw message