enschutz gem. Artt. 13-14
> DS-GVO durch Veröffentlichung auf unserer Internetseite unter:
> www.bauformat.de/datenschutz oder durch Zusendung auf Ihre formlose
> Anfrage.
>
> *Von:* Tomás Fernández Löbbe
> *Gesendet:* Freitag, 6. Dezember 2024 12:30
> *An:* users@solr.ap
Are you using the same schema for both cases? Is “businessId” a numeric
field or a String?
On Fri, Dec 6, 2024 at 7:53 AM Schmidt, Mihael
wrote:
> Hi Vincenzo,
>
>
>
> thanks for the info. There is the query parameters „shards“ which seems to
> let me choose the shard and replica.
>
>
>
> Best r
There may be improvements in this area since Solr 8.11, but last time I'd
seen it, I worked-around it by switching to http1. See this thread:
https://www.mail-archive.com/users@solr.apache.org/msg03272.html
On Thu, Jun 27, 2024 at 10:25 AM Paul Cote
wrote:
> To answer my own inquiry. This is a s
One thing you can use to influence ranking while still allowing the
optimization is to use Rank Fields[1]. Multiple field queries should be OK,
but I don't remember off the top of my head if DisMax queries work, I
believe they do, but I don't know why you wouldn't be seeing an improvement.
[1] ht
Are you asking a general question or did you see degradation and you are
trying to dig into it? Some more details can help people understand the
problem.
There is this Jira[1] I filed about a specific type of degradation with
highly distributed indices when using PKIAuthenticationPlugin
[1] https
Changing indexed=true/false or docValues=true/false on an existing field is
no longer allowed as of Solr 9 due to changes in Lucene[1]. You need to
reindex into a new index or at least a new field.
Tomás
[1] https://issues.apache.org/jira/browse/LUCENE-9334
On Mon, Aug 14, 2023 at 1:33 PM mtn s
Yes, good catch Andrei!
Mind filing a Jira issue?
On Tue, Apr 4, 2023 at 10:46 AM Shawn Heisey wrote:
> On 4/4/23 00:11, Andrei Minin wrote:
> > protected SolrClient getSolrClient(String baseUrl) {
> > return new
> Http2SolrClient.Builder(baseUrl).withHttpClient(httpClient).build();
> >
> Looking at the code in CloudHttp2SolrClient on main, branch_9x, and
> branch_9_2, the effective result of these two different options appear
> to be identical, the only difference being that the clientIsInternal
> boolean is false for the first option and true for the second. I would
> not expec
Hi Andrei,
Try replacing this:
builder = builder.withHttpClient(http2ClientBuilder.build());
with
builder = builder.withInternalClientBuilder(http2ClientBuilder);
Tomás
On Mon, Apr 3, 2023 at 10:13 AM Andrei Minin
wrote:
>
> Hi,
>
> I have an issue when using http2 solr client with SOLR (v9.0.
Hi Björn,
>
> 1.) Are these equivalent field definitions?
>
> Old:
>
> positionIncrementGap="0”/>
>
> New:
>
>
> 2.) Do we need to reindex after the scheme change?
>
> We have a large collections and are serving requests 24/7. Is a full index
> required or is Solr/Lucene able to handle both fiel
> Then, the long answer is that Apache Solr implements already approaches for
> 'early termination' such as Block Max WAND from Solr 8(thanks Lucene for
> this: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7148045/) to optimise
> query time and 'skip un-worthy candidates'.
>
Note that this is not
One way to achieve this without code changes in Solr is to provide the
"rid" parameter, you'd have to make your client add the "rid" parameter in
requests explicitly instead of (or in addition to) the x-correlation-id
header. The "rid" is logged in the different phases of the request, even in
the c
that ( I went from 6 to 16), but the issue still
> persists.
>
> I havent seen post commit events, where can I look for that ? Sorry, I'm
> relatively novice on configuring solr from scratch.
>
> Thanks in advance!
>
> ____
> From: Tomás F
Are you seeing any messages in the logs with "PERFORMANCE WARNING:
Overlapping onDeckSearchers"? Can you elaborate on the autowarm
configuration that you have? any "postCommit" events?
If you set the logger of "org.apache.solr.search.SolrIndexSearcher" to
DEBUG level you should see when the search
I have seen the same exception raised with search requests too. Not related
to traffic, since I've seen it in very low query rate cases. Also, not
related to resource utilization, since I've seen it in very under-utilized
clusters. An interesting part of the error is this:
> MultiplexConnectionPoo
15 matches
Mail list logo
