apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandesh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (APEXCORE-470) New Api for setting the attribute on the operator ( setOperatorAttribute )
Date Thu, 23 Jun 2016 04:39:16 GMT

     [ https://issues.apache.org/jira/browse/APEXCORE-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sandesh resolved APEXCORE-470.
------------------------------
       Resolution: Fixed
    Fix Version/s: 3.5.0

> New Api for setting the attribute on the operator ( setOperatorAttribute )
> --------------------------------------------------------------------------
>
>                 Key: APEXCORE-470
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-470
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Sandesh
>            Assignee: Sandesh
>             Fix For: 3.5.0
>
>
> Currently, *setAttribute* is used to set the operator attributes. Other 2 Attribute setting
APIs are specific to input ports (*setInputPortAttributes*) and output ports (*setOutputPortsAttributes*).
> Proposal is to have *SetOperatorAttribute* api, which will clearly indicate that user
wants set attributes on the operator.
> ( setOperatorAttribute(Operator operator, Attribute<T> key, T value) )
> Following will be the roles for the APIs
> *setAttributes* --> for setting Attributes for the whole DAG (  setAttribute(Operator
operator, Attribute<T> key, T value) - can be deprecated )
> *setOperatorAttributes* --> for setting Attributes for the operator 
> All the unit test cases using the previous API will be renamed as a part of this change.



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

Mime
View raw message