Hi team,
We need help with the strategy used to request data from solr cloud.
*Current Searching Strategy:*
We are using solr cloud 8.10 having 8 nodes with data sharded on the basis
of an implicit route parameter. We send a search http request on google's
network load balancer which divides reque
On 6/12/23 21:06, gnandre wrote:
Hi,
I am using Solr 9.2.1 (official docker image).
When I try to index a document, I get the error shown at the bottom of this
email.
I added your fieldType to a config, added a field using that type,
uploaded it to ZK, created a collection with that config,
Here is the corresponding stopwords.txt file content:
\# Licensed to the Apache Software Foundation (ASF) under one or more
\# contributor license agreements. See the NOTICE file distributed with
\# this work for additional information regarding copyright ownership.
\# The ASF licenses this f
Hi,
I am using Solr 9.2.1 (official docker image).
When I try to index a document, I get the error shown at the bottom of this
email.
Here is my corresponding filter setting
Thanks Shawn for your response!
Yes, we are on our way to indexing clients to SolrCloud 8 (and soon 9). We
have a massive Solr 6 deployment and it will take some time and so Solr 6
maintenance is still part of our job. We had not seen this error, but
recently a client complained of search failur
Hello everyone,
The CFP for *Community Over Code *(Formerly ApacheCon) is open until Thu, *13
July 2023 *23:59:59 GMT and wanted to remind you that we have a *Search
track.* Please submit your talks and share your stories here:
https://communityovercode.org/call-for-presentations/
A bit about the
On 6/12/23 10:24, mtn search wrote:
Any tips as to why this error is occurring? Occurs with query when sorting
on sortableSender or other fields with docvalues set to false. Plan to
re-index, but would like to better understand this issue. Why would it
expect "=SORTED" when docvalues is set to
Hello,
Any tips as to why this error is occurring? Occurs with query when sorting
on sortableSender or other fields with docvalues set to false. Plan to
re-index, but would like to better understand this issue. Why would it
expect "=SORTED" when docvalues is set to false?
Solr version 6.4.2
6
I use solr 7.1 in production right now. We use group
query to group on "query _type" field, and collapse on
"real _id" field so that we get unique real_ids in each
group (nullPolicy: expand).
I want to migrate to solr 9 but seems like using
collapse with group is deprecated. How can I
replicate the
There is also a new "maxSize" setting for autoCommit, that could perhaps be
used in place of maxDocs to prevent the trans-log growing too big, see
https://solr.apache.org/guide/solr/latest/configuration-guide/commits-transaction-logs.html#automatic-commits
I have seen the index. director
the reason autoCommit.maxTime is set to 5 mins is because of openSearcher=true
due to the TLOG + PULL replica types. Opening a new searcher too often is a
costly operation, especially during high traffic. When we were using NRT, the
autoCommit.maxTime was set to something like 60s and softCommit
11 matches
Mail list logo