Hi,<br><br>It's probably a question everyone knows the answer, but I'll ask anyway.<br><br>Make a UPDATE work on index, is not the same thing to do steps 2, 3 and 4? <span dir="ltr">Or UPDATE is computationally more expensive?</span> Or there is another reason to avoid the UPDATE?<br>
<br><br>Israel<br><br><div class="gmail_quote">On Wed, Jul 21, 2010 at 8:54 AM, Navin Surtani <span dir="ltr"><<a href="mailto:nsurtani@redhat.com">nsurtani@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just getting a discussion going on this since a JIRA has now been created.<br>
<br>
Basically, the way I see it is that we can check which keys in the cache<br>
have already been used - but that's context specific (I'll probably need<br>
a quick explanation to how the InvocationContexts work). The question<br>
for the gurus of ISPN here is whether or not this is going to be an issue.<br>
<br>
The plan of attack is as follows: -<br>
<br>
1 - User does a put()<br>
2 - Interceptor checks the set of keys used within the same context to<br>
see if the same key has been used<br>
3 - If it has an UPDATE is used.<br>
4 - If not we do an ADD.<br>
<br>
Reckon that sounds okay?<br>
<font color="#888888"><br>
--<br>
Navin Surtani<br>
Intern Infinispan<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</font></blockquote></div><br>