Thanks
From: Victor Dogaru <[email protected]>
To: [email protected]; [email protected]
Sent: Thursday, March 10, 2016 2:20 PM
Subject: Re: incubator-quarks git commit: QUARKS-20 counter_ops small, changed
oplet names, shortened tooltip timeout on hide
> does the topology graph that is returned always provided the same oplet
ids across multiple invocations?
Yes, for the current implementation, but not guaranteed by the current API:
public interface OpletContext<I, O> extends RuntimeServices {
/**
* Get the unique identifier (within the running job)
* for this oplet.
* @return unique identifier for this oplet
*/
String getId();
On Thu, Mar 10, 2016 at 2:06 PM, <[email protected]> wrote:
> That is a good point. I am using an index. If the graph's vertices are
> returned in a different order then it could change across invocations.
> I can modify the code to truncate the oplet id from OP_X to just X,
> thereby guaranteeing that the correlation between the displayed name and
> the oplet id are the same.
> However, I'm wondering does the topology graph that is returned always
> provided the same oplet ids across multiple invocations?
> Susan
> From: Dan Debrunner <[email protected]>
> To: "[email protected]" <[email protected]>
> Sent: Thursday, March 10, 2016 1:40 PM
> Subject: Re: incubator-quarks git commit: QUARKS-20 counter_ops small,
> changed oplet names, shortened tooltip timeout on hide
>
>
>
>
>
>
> > On Thursday, March 10, 2016 1:19 PM, "[email protected]" <
> [email protected]> wrote:
>
> > QUARKS-20 counter_ops small, changed oplet names, shortened tooltip
> timeout on
> > hide
>
> Looking at the code it seems the oplet name is changing from the oplet id
> to and index. Since oplet's don't have an index where does this value come
> from? Is it stable across multiple invocations of the application?
>
> Dan.
>
>
>
>
