Alex,

I tried to give regular expression on the partial operator name and it
works.

Eg:

<property>
    <name>dt.application.*.operator.hazel[\w].prop.host</name>
    <value>127.0.0.1</value>
</property>

Regards,
Ashwin.

On Mon, Aug 1, 2016 at 2:26 PM, David Yan <[email protected]> wrote:

> Hi Alex,
>
> You can make multiple operators sharing the same property by doing
> something like this:
>
> <property>
>    <name>your.own.property.name</name>
>    <value>127.0.0.1</value>
> </property>
>
> <property>
>    <name>dt.operator.opName1.prop.[property-name]</name>
>    <value>${your.own.property.name}</name>
> </property>
>
> <property>
>    <name>dt.operator.opName2.prop.[property-name]</name>
>    <value>${your.own.property.name}</name>
> </property>
>
> Or you can specify your.own.property.name's value at launch time.
>
> David
>
> On Mon, Aug 1, 2016 at 12:16 PM, McCullough, Alex <
> [email protected]> wrote:
>
>> Hey,
>>
>>
>>
>> I have an input and processing operator that both rely on hazelcast. I
>> defined a base operator where the setup method and common properties are
>> defined, each have an abstract class that extends this base operator to
>> handle default input or processing logic along with unique properties at
>> this level, and then of course each has a concrete implementation.
>>
>>
>>
>> Is there a way the two can share properties in the properties.xml? I know
>> you can wildcard some property/attribute descriptors, but could I wildcard
>> part of an operator name? meaning having an operator called hazelInput and
>> one called hazelProcess and a property defined as:
>>
>>
>>
>> <property>
>>     <name>dt.application.*.operator.hazel*.prop.host</name>
>>     <value>127.0.0.1</value>
>> </property>
>>
>>
>>
>> Thanks,
>>
>> Alex
>>
>> ------------------------------
>>
>> The information contained in this e-mail is confidential and/or
>> proprietary to Capital One and/or its affiliates and may only be used
>> solely in performance of work or services for Capital One. The information
>> transmitted herewith is intended only for use by the individual or entity
>> to which it is addressed. If the reader of this message is not the intended
>> recipient, you are hereby notified that any review, retransmission,
>> dissemination, distribution, copying or other use of, or taking of any
>> action in reliance upon this information is strictly prohibited. If you
>> have received this communication in error, please contact the sender and
>> delete the material from your computer.
>>
>
>


-- 

Regards,
Ashwin.

Reply via email to