I've done some experiments about indexing RefGuide (from source) into
Solr at: https://github.com/arafalov/solr-refguide-indexing . But the
problem was creating UI, hosting, etc.
There was also a thought (mine) of either shipping RefGuide in Solr
with pre-built index as an example or even just
On 10/28/2019 3:51 PM, Nicolas Paris wrote:
I am not very happy with the search engine embedded within the html
documentation I admit. Hope this is not solr under the hood :S
It's not Solr under the hood. It is done by a javascript library that
runs in the browser. It only searches page
> If you are someone who wishes the PDF would continue, please share your
> feedback.
I have not particularly explored the documentation format but the
content. However here my thought on this:
Pdf version of solr documentation has two advantages:
1. readable offline
2. make searching easier
Hi all -
Some have already noticed this change, but to state it formally, as of 8.2,
the Lucene PMC will no longer treat the PDF version of the Solr
Reference Guide as the primary format, and we will no longer release a PDF
version. The Guide will now be available online only.
Some of you may
I just saw this article.
https://issues.apache.org/jira/browse/SOLR-13349
Can my issue be related to this?
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
* Solr Version 7.7. Using Cloud with CDCR
* 3 replicas 1 shard on production and disaster recovery
Hi,
Last week, I posted a question about tlogs -
https://lucene.472066.n3.nabble.com/tlogs-are-not-deleted-td4451323.html#a4451430
I disabled buffer based on the advice, but still, tlogs in
* Solr Version 7.7. Using Cloud with CDCR
* 3 replicas 1 shard on production and disaster recovery
Hi,
Last week, I posted a question about tlogs -
https://lucene.472066.n3.nabble.com/tlogs-are-not-deleted-td4451323.html#a4451430
I disabled buffer based on the advice, but still, tlogs in
On 10/28/2019 9:30 AM, rhys J wrote:
Will I break Solr if i change this to default to not multi-valued?
If you are only indexing one value in those fields, then setting
multiValued to false will not break anything.
If an indexing request ever comes in that has more than one value for a
I forgot to include the fields created through the API:
Thanks,
Rhys
On Mon, Oct 28, 2019 at 11:30 AM rhys J wrote:
>
>
>> Did you reload the core/collection or restart Solr so the new schema
>> would take effect? If it's SolrCloud, did you upload the
> Did you reload the core/collection or restart Solr so the new schema
> would take effect? If it's SolrCloud, did you upload the changes to
> zookeeper and then reload the collection? SolrCloud does not use config
> files on disk.
>
So I have not done this part yet, but I noticed some things in
On 10/28/2019 7:23 AM, Danilo Tomasoni wrote:
We have a solr instance with around 40MLN docs.
In the bulk import phase we noticed a high IO and CPU load and it looks
like it's related to autocommit because if I disable autocommit the load
of the system is very low.
I know that disabling
Hello all,
We have a solr instance with around 40MLN docs.
In the bulk import phase we noticed a high IO and CPU load and it looks
like it's related to autocommit because if I disable autocommit the load
of the system is very low.
I know that disabling autocommit is not recommended, but I'm
There’s the preferredLeader property, see:
https://lucene.apache.org/solr/guide/6_6/collections-api.html
That said, this was put in for situations where there were 100s of shards with
replicas from many shards hosted on any given machine, so it was possible in
that setup to have 100 or more
Hello,
I'm looking for a way to configure my collections as such that the leader
nodes of specific collections never share the same host.
This as a way to prevent several large and/or heavy-usage collections on
the same machine.
Is this something I can set in solrconfig.xml? Or are there rules
14 matches
Mail list logo
