if anything is still unclear.
Thanks,
Matthew
On 6/25/18, 1:38 PM, "Shawn Heisey" wrote:
On 6/22/2018 12:14 PM, Matthew Faw wrote:
> So I’ve tried running MIGRATE on solr 7.3.1 using the following
parameters:
> 1) “split.key=”
> 2) “split.key=!”
&g
if this is part of the issue?
Thanks,
Matthew
On 6/22/18, 12:53 PM, "Shawn Heisey" wrote:
On 6/21/2018 9:41 AM, Matthew Faw wrote:
> Thanks for your reply. According to the MIGRATE documentation, the
split.key parameter is required, and removing it returns a missing parameter
exc
to me, it seems like this particular API endpoint does not work. I’d love
for someone to prove me wrong.
Thanks,
Matthew
On 6/21/18, 11:02 AM, "Shawn Heisey" wrote:
On 6/21/2018 7:08 AM, Matthew Faw wrote:
> For background, I’m using solr version 7.3.1 and lucene version 7.3.1
Hello,
For background, I’m using solr version 7.3.1 and lucene version 7.3.1
I have a solr collection with 2 shards and 3 replicas using the compositeId
router. Each solr document has “id” as its unique key, where each id is of
format DERP_${X}, where ${X} is some 24 character alphanumerical
Hi,
So I’ve been trying out the new autoscaling features in solr 7.2.1. I run the
following commands when creating my solr cluster:
Set up overseer role:
curl -s
"solr-service-core:8983/solr/admin/collections?action=ADDROLE=overseer=$thenode"
Create cluster prefs:
I sent this a few mins ago, but wasn’t yet subscribed. Forwarding the message
along to make sure it’s received!
From: Matthew Faw <matthew@verato.com>
Date: Thursday, March 15, 2018 at 12:28 PM
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Cc
