Re: gzip compression solr 8.4.1

, Johannes Am Do., 23. Apr. 2020 um 09:55 Uhr schrieb Johannes Siegert < johannes.sieg...@offerista.com>: > Hi, > > we want to use gzip-compression between our application and the solr > server. > > We use a standalone solr server version 8.4.1 and the prepackaged jetty

gzip compression solr 8.4.1

Hi, we want to use gzip-compression between our application and the solr server. We use a standalone solr server version 8.4.1 and the prepackaged jetty as application server. We have enabled the jetty gzip module by adding these two files: {path_to_solr}/server/modules/gzip.mod (see below the

ManagedFilter for stemming

Hi, we are using the SnowballPorterFilter to stem our tokens for serveral languages. Now we want to update the list of protected words over the Solr-API. As I can see, there are only solutions for SynonymFilter and the StopwordFilter with ManagedSynonymFilter and ManagedStopFilter. Do you know

Re: optimize cache-hit-ratio of filter- and query-result-cache

Thanks. The statements on http://wiki.apache.org/solr/SolrCaching#showItems are not explicitly enough for my question.

optimize cache-hit-ratio of filter- and query-result-cache

Hi, some of my solr indices have a low cache-hit-ratio. 1 Does sorting the parts of a single filter-query have impact on filter-cache- and query-result-cache-hit-ratio? 1.1 Example: fq=field1:(2 or 3 or 1) to fq=field1:(1 or 2 or 3) -> if 1,2,3 are randomly sorted 2 Does sorting the parts of

sort by given order

Hi, i want to sort my documents by a given order. The order is defined by a list of ids. My current solution is: list of ids: 15, 5, 1, 10, 3 query: q=*:*fq=(id:((15) OR (5) OR (1) OR (10) OR (3)))sort=query($idqsort) desc,id ascidqsort=id:((15^5) OR (5^4) OR (1^3) OR (10^2) OR

NGramTokenizer influence to length normalization?

Hi, does the NGramTokenizer have an influence to the length normalization? Thanks. Johannes

wrong docFreq while executing query based on uniqueKey-field

Hi. My solr-index (version=4.7.2.) has an id-field: field name=id type=string indexed=true stored=true/ ... uniqueKeyid/uniqueKey The index will be updated once per hour. I use the following query to retrieve some documents: q=id:2^2 id:1^1 I would expect that the document(2) should be

default query operator ignored by edismax query parser

Hi, I have defined the following edismax query parser: requestHandler name=/search class=solr.SearchHandler lst name=defaultsstr name=mm100%/strstr name=defTypeedismax/strfloat name=tie0.01/floatint name=ps100/intstr name=q.alt*:*/strstr name=q.opAND/strstr name=qffield1^2.0 field2/strstr

Re: default query operator ignored by edismax query parser

Thanks Shawn! In this case I will use operators everywhere. Johannes Am 25.06.2014 15:09, schrieb Shawn Heisey: On 6/25/2014 1:05 AM, Johannes Siegert wrote: I have defined the following edismax query parser: requestHandler name=/search class=solr.SearchHandler lst name=defaultsstr name

Bug within the solr query parser (version 4.7.1)

Hi, I have updated my solr instance from 4.5.1 to 4.7.1. Now the parsed query seems to be not correct. Query: /*q=*:*fq=title:TEdebug=true */ Before the update the parsed filter query is */+title:te +title:t +title:e/*. After the update the parsed filter query is */+((title:te

changed query behavior

Hi, I have updated my solr instance from 4.5.1 to 4.7.1. Now my solr query failing some tests. Query: q=*:*fq=(title:((TE)))?debug=true Before the update: lstname=debug strname=rawquerystring*:*/str strname=querystring*:*/str strname=parsedqueryMatchAllDocsQuery(*:*)/str

solr-query with NOT and OR operator

Hi, my solr-request contains the following filter-query: fq=((-(field1:value1)))+OR+(field2:value2). I expect solr deliver documents matching to ((-(field1:value1))) and documents matching to (field2:value2). But solr deliver only documents, that are the result of (field2:value2). I

Re: solr-query with NOT and OR operator

understand your goal. But generally, a purely negative nested query must have a *:* term to apply the exclusion against: fq=((*:* -(field1:value1)))+OR+(field2:value2). -- Jack Krupansky -Original Message- From: Johannes Siegert Sent: Tuesday, February 11, 2014 10:57 AM To: solr-user

Re: high memory usage with small data set

-lucenes-mmapdirectory-on-64bit.html Best, Erick On Wed, Jan 29, 2014 at 7:49 AM, Johannes Siegert johannes.sieg...@marktjagd.de wrote: Hi, we are using Apache Solr Cloud within a production environment. If the maximum heap-space is reached the Solr access time slows down, because of the working

high memory usage with small data set

on the heap-space-useage is between 50 and 90 percent. No OutOfMemoryException occurs. Questions: 1. Why does Solr use 5 GB ram, with this small amount of data? 2. Which impact does the large filter-queries have in relation to ram usage? Thanks! Johannes Siegert