[windup-dev] Where to store intermediate data?
Ondrej Zizka
ozizka at redhat.com
Fri Jul 25 14:44:51 EDT 2014
A rule, or perhaps during whole execution.
Actually those are 2 different things.
Currently, I need whole runtime scope - for Model metadata.
And also, I was thinking about a rule computing a sum of e.g. JMS queues
capacities (or anything such).
That would need an iteration, and within iteration, we have VarStack,
but that's only for WindupVertexFrames, so I was thinking what the user
has to store data like this, which are not to be reported.
Ondra
On 25.7.2014 20:39, Brad Davis wrote:
> Oh gotcha. So you mean like a map to pass data along during the execution of a rule itself?
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" <ozizka at redhat.com>
> To: windup-dev at lists.jboss.org
> Sent: Friday, July 25, 2014 2:21:47 PM
> Subject: Re: [windup-dev] Where to store intermediate data?
>
> Right, but Lincoln doesn't want the intermediate data in the graph, if I
> understand him correctly.
> That's why I am looking for some Map in our Java data structures.
>
> Ondra
>
>
>
> On 25.7.2014 20:11, Brad Davis wrote:
>> Alternative to adding data to the graph vertex directly, you could create a intermediate vertex that has a reference to another vertex you are referring to.
>>
>> IntermediateMapVertex -> SomeOtherVertex
>>
>> Brad Davis
>> Red Hat Consulting
>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>
>>
>> ----- Original Message -----
>> From: "Brad Davis" <bdavis at redhat.com>
>> To: "Windup-dev List" <windup-dev at lists.jboss.org>
>> Sent: Friday, July 25, 2014 2:09:57 PM
>> Subject: Re: [windup-dev] Where to store intermediate data?
>>
>> The Titan implementation already provides caching. When you say a Map like API, you mean to access the data on the nodes?
>>
>> >From an intermediate data perspective, you can always get the underlying vertex from the Framed Vertex, and then write to it like a Map (Key, Value pair).
>>
>> Brad Davis
>> Red Hat Consulting
>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>
>>
>> ----- Original Message -----
>> From: "Ondrej Zizka" <ozizka at redhat.com>
>> To: "Windup-dev List" <windup-dev at lists.jboss.org>
>> Sent: Friday, July 25, 2014 2:02:06 PM
>> Subject: [windup-dev] Where to store intermediate data?
>>
>> Hi,
>>
>> where should I cache intermediate data? E.g. the model metadata.
>> I expected GraphContext to have some Map-like API, there's none.
>> Should I add it? Or should I clutter the API with it? Or will it be
>> better to store it in the graph afterall?
>>
>> Thanks,
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
More information about the windup-dev
mailing list