Thanks!
Jae
On Fri, Dec 4, 2020 at 1:38 AM Radu Gheorghe
wrote:
> Hi Jae,
>
> No, it’s not smarter than explicitly defining, for example enum for a
> low-cardinality field.
>
> Think of “smart” as a default path, and explicit definitions as some
> “hints”. You can see that default path in this
This almost always a result of one of two things:
1> you didn’t upload the config to the correct place or the ZK that Solr uses.
or
2> you still have a syntax problem in the config.
The solr.log file on the node that’s failing may have a more useful
error message about what’s wrong. Also, you can
I wonder if you could increase the precision of your result set to reduce
its size? If you have 10M results for a query but only the first 10K
deserve to be represented by the faceting, what is it about those 10K that
makes them better than the other 9.99M? For example if some items are
boosted by
Hi,
When trying to modify the config.xml file for a collection I made a mistake
and the config was wrong. So I removed the collection to create it again
from a backend.
But, although I'm sure I'm using a correct config.xml, solr is still
complaining about the error in the older solrconfig.xml
I h
Are you stuck in iowait during that commit?
On Fri, Dec 4, 2020 at 6:28 AM raj.yadav wrote:
>
> Hi everyone,
>
> As per suggestions in previous post (by Erick and Shawn) we did following
> changes.
>
> OLD CACHE CONFIG
> size="32768"
> initialSize="6000"
>
To expand on Shawn’s comment. There are a lot of built-in helper methods in
SolrJ, but
they all amount to setting a value in the underlying map of params, which you
can
do yourself for any parameter you could specify on a URL or cURL command.
For instance, SolrQuery.setStart(start) is just:
thi