apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Weise <tho...@datatorrent.com>
Subject Re: Proposed Changes To Apex Property Files
Date Wed, 09 Sep 2015 01:40:52 GMT
How would you handle the case where two attributes with the same name exist
in the hierarchy, for example CHECKPOINT_WINDOW_COUNT (DAG and
OperatorContext)?

Is the proposed change backward compatible?


On Tue, Sep 8, 2015 at 5:44 PM, Timothy Farkas <tim@datatorrent.com> wrote:

> Hello all,
>
> This JIRA https://malhar.atlassian.net/browse/APEX-28 is proposing a
> change
> to the way attributes are declared in properties files. The proposal will
> allow a short form declaration of properties, and supports the following
> features:
>
> 1 - Root attribute declaration
>
> dt.attr.MEMORY_MB is now a valid property and will set the MEMORY_MB
> attribute for all operators
>
> 2 - Ambiguous property handling
>
> dt.attr.AUTO_RECORD will set the AUTO_RECORD attribute on both operators
> and ports
>
> 3 - Fully qualified attribute names
>
> Attribute names can be prefix with the name of their Context class
>
> dt.attr.com.datatorrent.api.Context.PortContext.AUTO_RECORD will set the
> AUTO_RECORD attribute for all ports
>
> 4 - Child attributes can be specified on parent elements
>
> dt.attr.application.*.attr.MEMORY_MB will set the MEMORY_MB attribute on
> all operators
>
> 5 - Existing methods for setting properties are supported.
>
> An implementation of this is pending review here:
> https://github.com/apache/incubator-apex-core/pull/11
>
> Please provide your feedback.
>
> Thanks,
> Tim
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message