You can send big queries as a POST request instead of a GET request.
Op do 18 feb. 2021 om 11:38 schreef Anuj Bhargava :
> Solr 8.0 query length limit
>
> We are having an issue where queries are too big, we get no result. And if
> we remove a few keywords we get the result.
>
> Error we get -
Hi,
In Solr 8.6.1, a GET request or a HEAD request for a non-existing term in a
managed resource (stopword or synonym) returns a HTTP status "404 Not
Found".
$ curl -i "
http://localhost:8983/solr/techproducts/schema/analysis/synonyms/english/foobar;
| head -n 1
HTTP/1.1 404 Not Found
$ curl -I
Hi Steve
I have a real-world use case. We don't apply a synonym filter at index
time, but we do apply a managed synonym filter at query time. This allows
content managers to add new synonyms (or remove existing ones) "on the fly"
without having to reindex any documents.
Thomas
Op do 10 sep.
Hi,
I'm trying to configure the Rule-Based Authorization Plugin in Solr 8.4.0
in standalone mode. My goal is to limit a user's access to one or more
designated cores. My security.json looks like this:
{
"authentication":{
"blockUnknown":true,
"class":"solr.BasicAuthPlugin",
Do keep this paragraph from the docs in mind when switching from a
non-graph to a graph filter:
If you use this filter during indexing, you must follow it with a Flatten
Graph Filter to squash tokens on top of one another like the Synonym
Filter, because the indexer can’t directly consume a
Hi,
Is it possible to specify a Tokenizer Factory on a Managed Synonym Graph
Filter? I would like to use a Standard Tokenizer or Keyword Tokenizer on
some fields.
Best,
Thomas
Op vr 3 jul. 2020 om 14:11 schreef Bram Van Dam :
> On 03/07/2020 09:50, Thomas Corthals wrote:
> > I think this should go in the ref guide. If your product depends on this
> > behaviour, you want reassurance that it isn't going to change in the next
> > release. Not eve
I think this should go in the ref guide. If your product depends on this
behaviour, you want reassurance that it isn't going to change in the next
release. Not everyone will go looking through the javadoc to see if this is
implied.
Typically it'll either be something like "are always returned in
Since "overseer" is also problematic, I'd like to propose "orchestrator" as
an alternative.
Thomas
Op vr 19 jun. 2020 04:34 schreef Walter Underwood :
> We don’t get to decide whether “master” is a problem. The rest of the world
> has already decided that it is a problem.
>
> Our task is to
Can anybody shed some light on this? If not, I'm going to report it as a
bug in JIRA.
Thomas
Op za 13 jun. 2020 13:37 schreef Thomas Corthals :
> Hi
>
> I'm seeing different ordering on the spellcheck suggestions in cloud mode
> when using spellcheck.extendedResu
Hi
I'm seeing different ordering on the spellcheck suggestions in cloud mode
when using spellcheck.extendedResults=false vs.
spellcheck.extendedResults=true.
Solr 8.5.2 in cloud mode with 2 nodes, 1 collection with numShards = 2 &
replicationFactor = 1, techproducts configset and example data:
If your XML or JSON can't be parsed, your content never makes it to the
update chain.
It looks like you're trying to index non-UTF-8 data. You can set the
encoding of your XML in the Content-Type header of your POST request.
-H 'Content-Type: text/xml; charset=GB18030'
JSON only allows UTF-8,
}]'
{
"responseHeader":{
"rf":2,
"status":0,
"QTime":81}}
$ curl '
http://localhost:8983/solr/techproducts/select?q=id%3A123=true'
{
"response":{"numFound":1,"start":0,"docs":[
{
"id":"123",
"cat":["a",
"b",
"c",
"a",
"b",
"d"],
"_version_":1668919799351083008}]
}}
Is this a known issue or am I missing something here?
Kind regards
Thomas Corthals
Hi
I've run into an issue with creating a Managed Stopwords list that has the
same name as a previously deleted list. Going through the same flow with
Managed Synonyms doesn't result in this unexpected behaviour. Am I missing
something or did I discover a bug in Solr?
On a newly started solr
14 matches
Mail list logo
