I too have felt this was an oddity. +1 for the change with deprecation. However do note that attributes are layered and port attributes or operator attributes can be specified at the DAG level and they apply globally within the scope.
Thanks On Mon, Jun 6, 2016 at 1:39 PM, Sandesh Hegde <[email protected]> wrote: > 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 > > Let me know your thoughts. > > Thanks >
