Hello again;
I have managed to reproduce the issue in a unit test. I should probably add a
Jira ticket with a patch for the unit test On Solr 8.5.0, not master.
Meanwhile, for your suggested queries:
1. Query on the collection:
curl -i -u admin:admin
I’d say, try the query with curl and enable http headers
curl -i —user admin:admin http://localhost:8983/solr/mycollection/select?q=*:*
curl -i —user admin:admin http://localhost:8983/solr/myalias/select?q=*:*
Are you saying that you see a difference between the two? What are the headers?
Jan
Recently we found strange behavior in a query. We use eDismax as the query
parser.
This is the query term:
1,3-DIMETHYL-5-(3-PHENYL-ALLYLIDENE)-PYRIMIDINE-2,4,6-TRIONE
It should hit one document in our index. It does not. However, if you use the
Dismax query parser it does match the record.
Hi Jan
Thank you for your time on this.
If I send a /select request directly on the alias (/solr/test/select), the
browser asks for credentials, but the Solr response returns status=401 and an
html error message with "HTTP ERROR 401 require authentication"
Obviously, my expectation was that
I question whether fiterCache has anything to do with it, I suspect what’s
really happening is that first time you’re reading the relevant bits from disk
into memory. And to double check you should have docVaues enabled for all these
fields. The “uninverting” process can be very expensive, and
I feel the mentioned issue is more or less relavant to following JIRA. Any idea
on this?
https://issues.apache.org/jira/browse/SOLR-13458
Thanks & Regards,
Vinodh
From: Kommu, Vinodh K.
Sent: Wednesday, June 10, 2020 10:43 PM
To: solr-user@lucene.apache.org
Subject: RE: Timeout issue while
We've run the performance test after changing the fields to be of the type
string. We're seeing improved performance, especially after the first time the
query has run. The first run is taking around 1-2 seconds rather than 6-8
seconds and when the filter cache is present, the response time is
Using solr 8.2.0 and setup a cloud with 2 nodes. (2 replica's for each
collection)
Enabled basic authentication and gave all access to the admin user
Now trying to use solr cloud backup/restore API, backup is working great,
but when trying to invoke restore API its throwing the below error
{
Hi,
Solr has been a sub-project of the Lucene TLP, but wil separate releases, JIRA,
user-list etc.
The committers have decided to establish Solr as a separate Apache Top Level
Project (TLP).
Please see the VOTE thread on the DEV mailing list:
https://s.apache.org/solr-tlp-vote
Hi
I tried to reproduce, but I can successfully search both the collection and the
alias. Both collection and alias promt for password, and when giving the
password the search succeeds.
What was your expectation?
Jan
> 11. jun. 2020 kl. 16:53 skrev Isabelle Giguere
> :
>
> Some extra info:
10 matches
Mail list logo
