Hi,
524 or 504 both refer to timeouts, but both are meant for proxies (so
reverse proxy can't reach the backend server in time). So both of them
do not match.
408 is "request timeout", but that's client's fault (4xx code). In that
case its a more technical code because it also requires to cl
Hi,
in Lucene we have similar (production code) which disables the vector
API when the default locale has Turkish "i" problems on certain JVMs:
https://github.com/apache/lucene/blob/04dd8d32afcdc4f0798647f173db2924a3d38b42/lucene/core/src/java/org/apache/lucene/internal/vectorization/Vectoriza
Hey all,
It's time once again to start thinking ahead to our Virtual Meetup for
March! (Apologies for starting this discussion a bit late this month, as
I've been afk for a few weeks.)
Since we are pretty far into the month I'll volunteer to organize the
meeting for March, so all we need to do i
Agree on all of Uwe's points below
I think 500 is the most appropriate for exceeding QueryLimits --
unless/until we decie we want Solr to start using custom response codes in
some cases, but in that case i would suggest we explicitly *avoid* using
504, 524, & 529 precisely because they alread
https://issues.apache.org/jira/browse/SOLR-17207
: Date: Tue, 19 Mar 2024 10:31:54 +0100
: From: Uwe Schindler
: To: Chris Hostetter , dev@solr.apache.org
: Subject: Re: LocaleTest fails only on thetaphi CI
:
: Hi,
:
: in Lucene we have similar (production code) which disables the vector API
I still think 503 is appropriate when timeAllowed is exceeded. The service
requested is a reponse within the set time. That service is not available. Here
are the RFC definitions of 500 and 503. Exceeding timeAllowed isn’t an
“unexpected condition”, it is part of the normal operation of that lim
I'm glad I raised this topic -- great feedback from all of you!
I suppose we could indeed use a new/unused response code. Making it
configurable seems fine but I'd only want to support arcane things
like that in the most basic way, e.g. using the new EnvUtils.
Walter's response really resonates
I’m sure I’m being stupid, but I can’t figure out in which way.
Within the last month or so, I’ve built a project that uses maven2 to get
dependencies, with my POM listing things like
org.apache.lucene
lucene-test-framework
8.12.2
…along with solr-core, solr-analysis-
On 3/19/2024 21:51, Bill Dueber wrote:
Tonight I went to build my project and maven gives me and error like, e.g., The
POM for org.apache.solr:solr-analysis-extras:jar:8.12.2 is missing, no
dependency information available
So I bop on over to maven central, and sure enough, it only goes up throug
