l difference.
>
> Best,
> Erick
>
> > On Jul 20, 2020, at 10:04 AM, Jason J Baik
> wrote:
> >
> > Our use case here is that we want to highlight a single document (against
> > user-provided keywords), and we know the document's unique key already.
&
n to ping a specific replica _only_ (I’ve often done this
> for
> troubleshooting), address the full replica and add “distrib=false”, i.e.
> http://…../solr/collection1_shard1_replica1?q=*:*&distrib=false
>
> Best,
> Erick
>
> > On Jul 20, 2020, at 9:02 AM, Jason J Baik
Hi,
After upgrading from Solr 6.6.2 to 7.6.0, we're seeing an issue with
request routing in CloudSolrClient. It seems that we've lost the ability to
route a request to a specific core of a node.
For example, if a host is serving shard 1 core 1, and shard 2 core
1, @6.6.2, adding a "_route_="
para
This might be of interest to you:
https://issues.apache.org/jira/browse/LUCENE-8776
On Mon, May 27, 2019 at 10:32 PM Zheng Lin Edwin Yeo
wrote:
> How are you indexing the message, or what is the command that you used to
> index the message?
>
> Also, the attachment might not make it to the serve
This seems related to https://issues.apache.org/jira/browse/SOLR-11503?
On Thu, Mar 28, 2019 at 2:14 AM vishal patel
wrote:
>
> Hi
>
> I am upgrading the solr 8.0.0 from 6.1.0. Before I can not add the
> coreNodeName in core.properties and its working fine for me. But when i
> start the solr 8.
