Hello all,
With HSEARCH-761 each index can be configured with a separate backend;
one possible configuration is a "multi-master" in which LuceneWork
operations related to different indexes are sent to different
backends, possibly on different cluster nodes but not necessarily.
So while before the
For JMS I also would use a message property. That's what they are for.
--Hardy
On Fri, 22 Jul 2011 14:11:48 +0200, Sanne Grinovero
wrote:
> Hello all,
> With HSEARCH-761 each index can be configured with a separate backend;
> one possible configuration is a "multi-master" in which LuceneWork
I've made some progress on the abstraction contract between OGM and the
underlying store.
I've introduced the notion of Tuple that can then be converted in whatever the
store pleases (AtomicMap for example in Infinispan's case).
Let me know if you think that's going in the right direction
https:
No opinion.
On 22 juil. 2011, at 14:11, Sanne Grinovero wrote:
> Hello all,
> With HSEARCH-761 each index can be configured with a separate backend;
> one possible configuration is a "multi-master" in which LuceneWork
> operations related to different indexes are sent to different
> backends, pos
