Basically, you have to re-index whenever you change the schema,
with very few exceptions. Some changes cause exceptions.
Some changes just fail to return the correct results. Etc.
You can _add_ completely new fields without reindexing, but
they won't have any values for existing documents. You can
Do we need to reindex if we change synonymQueryStyle values for a fieldType ?
I hope not.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi Eric, Found the reason and all shard request to go /select flow solves the
problem.
Regarding
In SOLR 7 when relevancy added for the search it is not working (not
expected results) for the above fieldtype but same works fine for /select
because it uses Lucene Parser but our flow uses EDISMAX.
I can’t find the original post right now, but putting a load balancer in front
of
Zookeeper is a really bad idea. Do not do that. There is a stateful protocol
between one client and one Zookeeper node. This is not a stateless protocol
that you can just bounce around between servers.
wunder
Walter
bq. 2. Did you take the solrconfig that came with 7.5 and modify it rather
than copy your 5.3 solrconfig?
No, We have adjusted existing 5.3.1 config when we used for couple years to
SOLR 7.5.0.
I don't think this is the root of your problem, but this is always
suspect. Not only
can the format of s
You may of course ignore the warning in the UI, it is just a warning intended
to help you avoid mis-configurations.
But there may be side effects of placing a load balancer in between client and
zk cluster, see
https://stackoverflow.com/questions/30905007/load-balancer-with-zookeeper
--
Jan Høyd
Thanks Erick, I was waiting your Day time appears to get suggestion because
you are very spontaneous for this great open source community.
1. Did you recompile and redistriburte your custom component?
* Yes*
2. Did you take the solrconfig that came with 7.5 and modify it rather
than copy you
Thanks Jan, I am unaware how our Devops team decided this But this was
working well without any issues with SOLR 5.3.1 for couple of years. Just
wanted to make any changes in SOLR7 mandates .
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
1. Did you recompile and redistriburte your custom component?
2. Did you take the solrconfig that came with 7.5 and modify it rather
than copy your 5.3 solrconfig?
3. Did you reindex from scratch with 7x? Lucene/Solr guarantees only
one major version back-compat.
Best,
Erick
On Wed, Feb 13, 2019
You need to list all zk hosts in zkHost, that’s part of the design for ZK,
clients will open connections to all nodes and be able to fail over if trouble.
Where did you get the CNAME advice?
Jan Høydahl
> 13. feb. 2019 kl. 05:56 skrev ramyogi :
>
> We are migrating SOLR version, We used 3 ZK h
We are migrating SOLR version, We used 3 ZK hosts that configured to SOLR as
ZK connection string: zookeeper.solrtest.net:2181/test-config
Ensemble size: 1
Ensemble mode: ensemble
zookeeper.solrtest.net:2181
ok true
clientPort 2181
zk_server_state follower
zk_version 3.4.5
zk_approx
11 matches
Mail list logo
