GitHub user ilooner opened a pull request:
https://github.com/apache/incubator-apex-core/pull/11
Apex 28 pull latest
JIRA: https://malhar.atlassian.net/browse/APEX-28
Summary of Work:
This pull request simplifies the way properties for attributes can be
specified in a properties file. Specifically it allows the specification of
child level attributes within a parent context. For example it
is now possible to define the MEMORY_MB attribute for operators by defining
the following attribute
dt.attr.MEMORY_MB. This pull request also provides handling for ambiguous
attribute names. Please see the JIRA for details.
I also added Validation to check to make sure that Attributes with the same
name defined in multiple contexts will have the same type.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilooner/incubator-apex-core
APEX-28_pull_latest
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/11.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #11
----
commit 434a7170e4a4e2da013e283706b5bf42f853f6a4
Author: Timothy Farkas <[email protected]>
Date: 2015-08-11T17:50:57Z
APEX-28 #resolve
- Added the ability to specify attributes in a properties xml as
dt.attr.MY_ATTR
- Added handling for ambiguous attributes
- Added the ability to specify attributes for operators and ports on parent
elements like applications
- Cleaned up commented out code and warnings in LogicalPlanConfiguration
commit 7aab47a17b5e8628ce6c048f42abb133f983fb15
Author: Timothy Farkas <[email protected]>
Date: 2015-08-26T01:03:08Z
APEX-28 #resolve
- Rename of files requires a separate commit to preserve attribution.
- Improved documentation
- Added unit test to make sure that attributes declared in multiple
contexts have the same type.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
