[
https://issues.apache.org/jira/browse/APEXCORE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995261#comment-15995261
]
Thomas Weise commented on APEXCORE-234:
---------------------------------------
I think that the current approach of setting properties on operators, while
flexible, does not provide the required level of abstraction. There should be
support for application level properties, including complex objects, and the
application assembly should set these properties on whatever operators need
them. This is pretty much what happens with modules today, and perhaps
applications can be seen like modules without ports?
JSON or YAML might be good formats to configure applications.
> Investigate other ways to specify properties in property files
> --------------------------------------------------------------
>
> Key: APEXCORE-234
> URL: https://issues.apache.org/jira/browse/APEXCORE-234
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Pramod Immaneni
> Labels: roadmap
>
> The current property file specification follows the hadoop configuration file
> format and this has led to some drawbacks.
> a. The names for the properties and attributes are verbose in the
> configuration file.
> b. When there are nested properties in operators the syntax deviates from
> the bean specification because it introduces some specific keywords in the
> specification like .prop and ,attr.
> There will already be some changes afoot based on the following
> a. When adding ability to specify single instance attributes
> (https://malhar.atlassian.net/browse/APEXCORE-233) implementing it in the
> current syntax may not be possible or lead to very unwieldy syntax.
> b. There are also other ideas such as one from David to have the ability
> to specify global application level attributes which possible require
> rethinking the current syntax.
> Users have also asked for an easier and more consistent way to specify these
> properties. This issue is to track the ideas and progress of these changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
