[infinispan-dev] [ISPN-548] Discussion on updating the QueryInterceptor to be able to update old keys

[Israel Lacerra]

Hi,

It's probably a question everyone knows the answer, but I'll ask anyway.

Make a UPDATE work on index, is not the same thing to do steps 2, 3 and 4? Or
UPDATE is computationally more expensive? Or there is another reason to
avoid the UPDATE?


Israel

On Wed, Jul 21, 2010 at 8:54 AM, Navin Surtani <nsurtani at redhat.com> wrote:

> Just getting a discussion going on this since a JIRA has now been created.
>
> Basically, the way I see it is that we can check which keys in the cache
> have already been used - but that's context specific (I'll probably need
> a quick explanation to how the InvocationContexts work). The question
> for the gurus of ISPN here is whether or not this is going to be an issue.
>
> The plan of attack is as follows: -
>
> 1 - User does a put()
> 2 - Interceptor checks the set of keys used within the same context to
> see if the same key has been used
> 3 - If it has an UPDATE is used.
> 4 - If not we do an ADD.
>
> Reckon that sounds okay?
>
> --
> Navin Surtani
> Intern Infinispan
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20100721/ed511268/attachment.html