apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandesh Hegde <sand...@datatorrent.com>
Subject Re: Proposal : DAG - SetOperatorAttribute
Date Mon, 20 Jun 2016 16:54:43 GMT
Hi All,

This change has been merged, will be part of 3.5.

New API in the DAG, setOperatorAttribute(Operator operator, Attribute<T> key,
T value) )
Another API was deprecated, "setAttribute(Operator ... "

Thanks



On Tue, Jun 7, 2016 at 1:08 PM Sandesh Hegde <sandesh@datatorrent.com>
wrote:

> I have created a Jira, will start working on this.
>
> https://issues.apache.org/jira/browse/APEXCORE-470
>
>
>
> On Tue, Jun 7, 2016 at 12:21 PM Munagala Ramanath <ram@datatorrent.com>
> wrote:
>
>> +1
>>
>> Since we have *setInputPortAttribute* and *setOutputPortAttribute*, it
>> seems reasonable
>> to add *setOperatorAttribute*.
>>
>> Ram
>>
>> On Mon, Jun 6, 2016 at 1:39 PM, Sandesh Hegde <sandesh@datatorrent.com>
>> 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
>> >
>>
>

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