PM
To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org>
Subject: Re: Searches across Cores
For some good reasons, SolrCloud is not an option for me.
I need to run nested graph queries so firing parallel queries and taking
union/intersection won't work.
I am aware of achievin
nt, however, the document will be
rejected. You could also use the _route_ parameter to name a specific shard."
--
Vadim
> -Original Message-
> From: Komal Motwani [mailto:motwani.ko...@gmail.com]
> Sent: Friday, August 09, 2019 7:57 PM
> To: solr-user@lucene.apache.org
> Sub
For some good reasons, SolrCloud is not an option for me.
I need to run nested graph queries so firing parallel queries and taking
union/intersection won't work.
I am aware of achieving this via shards however I am looking for ways to
achieve this via multiple cores. We already have data existing
So my question is why do you have individual cores? Why not use SolrCloud and
collections and have this happen automatically?
There may be very good reasons, this is more if a sanity check….
> On Aug 9, 2019, at 8:02 AM, Jan Høydahl wrote:
>
> USE request param =core1,core2 or if on separate
USE request param =core1,core2 or if on separate machines
host:port/solr/core1,host:port/solr/core2
Jan Høydahl
> 9. aug. 2019 kl. 11:23 skrev Komal Motwani :
>
> Hi,
>
>
>
> I have a use case where I would like a query to span across Cores
> (Multi-Core); all the cores involved do have
Hi,
If the number of cores spanned is low, I guess firing parallel queries and
taking union or intersection should work since their schema is the same. Do
you notice any perceivable difference in performance?
Best,
Sidharth
On Fri, Aug 9, 2019 at 2:54 PM Komal Motwani
wrote:
> Hi,
>
>
>
> I
Hi,
I have a use case where I would like a query to span across Cores
(Multi-Core); all the cores involved do have same schema. I have started
using solr just recently and have been trying to find ways to achieve this
but couldn’t find any solution so far (Distributed searches, shards are not
