Using my strategy (create ReplicableCommand in CacheQueryImpl and then use RpcManager to broadcast the query), I'm having troubles getting the local Cache instance on each node. If I try to use CommandsFactory to initialize my replicableCommand, I create a undesired dependency: infinispan-core -> infinispan-query.<br>
<br>I need the Cache instance to get component registry and then get SearchFactoryImplementor to make the query.<br><br>Is there a way to get the local cache instance? <br><br>Someone has something to say about the way I'm solving it? Perhaps it's not the best way... <br>
<br><br>thanks!<br><br>Israel Lacerra<br>
<br><div class="gmail_quote">On Sat, Jun 19, 2010 at 9:31 PM, Israel Lacerra <span dir="ltr"><<a href="mailto:israeldl@gmail.com" target="_blank">israeldl@gmail.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;">
Ok! Understood.<br><br>So I'll try to use RpcManager to broadcast the query.<br><br>Thanks!<br><font color="#888888">Israel</font><div><div></div><div><br><br><div class="gmail_quote">On Fri, Jun 18, 2010 at 6:42 PM, Manik Surtani <span dir="ltr"><<a href="mailto:manik@jboss.org" target="_blank">manik@jboss.org</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;"><div><br>
On 9 Jun 2010, at 05:45, Israel Lacerra wrote:<br>
<br>
> Manik,<br>
><br>
> About the "map" part of the map/reduce of ISPN-200.<br>
><br>
> Looking in the code, my intention is(briefly) create a ReplicableCommand in CacheQueryImpl and then use RpcManager to make the query on all nodes.<br>
><br>
> But ISPN-200 depends on ISPN-39, right?<br>
<br>
</div>Well, not precisely. They are related and a degenerate case of ISPN-39 *could* work for you, but isn't necessary. Let me explain:<br>
<br>
ISPN-39 is about pushing tasks to nodes based on key. So, you may say something like, here's a task, T, which requires keys K1, K2, K3. The DistributionManager could then be used to determine the most appropriate node(s) to send T to, and process it there.<br>
<br>
Now in the case of ISPN-200, you don't know which nodes contain the entries you are looking for. So you would need to broadcast the task, T, which in this case is a query task, to *all* nodes. So while it is similar to ISPN-39 in that it executes remote tasks, the logic of determining which nodes to execute the task on is different - you would need to execute the task on all nodes all the time.<br>
<br>
Hope this clarifies things a bit. :)<br>
<br>
Cheers<br>
Manik<br>
<div><br>
> This dependecy is about the map part? The idea behind ISPN-39 is to migrate a computation to other nodes? Like a "continuation"? And then ISPN-200 will use this api to make the query on all nodes?<br>
><br>
><br>
> thanks!<br>
><br>
> Israel<br>
><br>
><br>
</div>> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">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>
<br>
--<br>
Manik Surtani<br>
<a href="mailto:manik@jboss.org" target="_blank">manik@jboss.org</a><br>
Lead, Infinispan<br>
Lead, JBoss Cache<br>
<a href="http://www.infinispan.org" target="_blank">http://www.infinispan.org</a><br>
<a href="http://www.jbosscache.org" target="_blank">http://www.jbosscache.org</a><br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">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>
</blockquote></div><br>
</div></div></blockquote></div><br>