e filter-out queries that contain too many non-alphanumeric characters
> before sending the request to Solr ? Whatever "too many" could be.
>
> Isabelle Giguère
> Computational Linguist & Java Developer
> Linguiste informaticienne & développeur java
>
>
>
Hi,
Environment: SolR 6.6.2, with org.apache.solr.solr-core:6.1.0. This setup has
been running for at least 4 years without having OutOfMemory error. (it is
never too late for an OOM…)
This week, our search tool has been attacked via ‘sql injection’ like, and that
led to an OOM. These requests
lly now it works, however I am just scared this is not correct or bad
practice as I am dealing with IDs and they should be anyhow parsed.
What is your opinion ?
Thanks
Guilherme
> On 18 Nov 2019, at 15:42, Guilherme Viteri wrote:
>
> Hi,
>
>> Have you tried reindexing t
ng terms in q by 100x. Since
> your terms don't match with the values in dbId for any document, the score
> produced by this scoring is 0. 100x or 1x of 0 is still 0.
> I still need to see how this scoring gets added up in edismax parser but do
> reevaluate the usage of these qfs. S
ocument with those impacting the result in
> qf.
>
>> On Tue, 12 Nov 2019 at 16:14, Guilherme Viteri wrote:
>> What I can't understand is:
>> I search for the exact term - "Immunoregulatory interactions between a
>> Lymphoid and a non-Lymphoid cell" and
gt; On 11 Nov 2019, at 12:24, Guilherme Viteri wrote:
>
> Thanks
>> Removing stopwords is another story. I'm curious to find the reason
>> assuming that you keep on using stopwords. In some cases, stopwords are
>> really necessary.
> Yes. It always make sense the
t;>>>> people have been able to substitute synonyms and/or shingles to make
>>> this
>>>>> work at the expense of a larger index.
>>>>>>
>>>>>> This is a generic problem with context. “Lamin A” is really a
>>> “concept”,
; On Fri, Nov 8, 2019 at 11:30 AM Guilherme Viteri wrote:
>
>> HI Walter and Paras
>>
>> I indexed it removing all the references to StopWordFilter and I went from
>> 121 results to near 20K as the search term q="Lymphoid and a non-Lymphoid
>> cell" is m
With the the two radically different system getting the same number,
> I decided that was a property of the documents, not of the search engines.
>
> wunder
> Walter Underwood
> wun...@wunderwood.org <mailto:wun...@wunderwood.org>
> http://observer.wunderwood.org/ <http://observer
hat.
>
> In your edismax handlers, weights of 20, 50, and 100 are extremely high. I
> don’t think I’ve ever used a weight higher than 16 in a dozen years of
> configuring Solr.
>
> wunder
> Walter Underwood
> wun...@wunderwood.org
> http://observer.wunderwood.
JSON output as you have sent but this time with
> *"echoParams=all"*. Also, post the exact Solr query url.
>
>
>
> On Wed, 6 Nov 2019 at 21:07, Erick Erickson wrote:
>
>> I don’t see the attachments, maybe I deleted old e-mails or some such. The
>&
t; The solr.StopFilter removes all tokens that are stopwords. Those words
>>> will not be in the index, so they can never match a query.
>>>
>>> 1. Remove the lines with solr.StopFilter from every analysis chain in
>>> schema.xml.
>>> 2. Reload the colle
rally axe any reference
> to them at all
>
> On Tue, Nov 5, 2019 at 9:47 AM Guilherme Viteri wrote:
>
>> Thanks.
>> Haven't I done this here ?
>> > positionIncrementGap="100" omitNorms="false" >
>>
>>
ce to stop words and
> never use them, then re-index your data and try it again.
>
> On Tue, Nov 5, 2019 at 9:14 AM Guilherme Viteri wrote:
>
>> Hi,
>>
>> I am performing a search to match a name (text_field), however this term
>> contains 'and' and
Hi,
I am performing a search to match a name (text_field), however this term
contains 'and' and 'a' and it doesn't return any records. If i remove 'a' then
it works.
e.g
Search Term: lymphoid and a non-lymphoid cell
doesn't work:
https://dev.reactome.org/content/query?q=lymphoid+and+a+non-lymph
15 matches
Mail list logo
