Hello,
I'm trying to find a solution for multiwords synonyms in solr 9.2.1.
We cannot use sow=false because our different fields have different
stopwords and synonyms, ie they are not consistently analyzed and we dont
want SolR to use a field centric query ((as explained here:
https://opensourcec
ption, then suddenly a surprising query structure can be
output by the user adding “the” to their search."
Le mar. 7 mai 2024 à 16:30, elisabeth benoit a
écrit :
>
> For the record, I solved this problem by removing stop words in my
> analyzer for wordfield.
>
> We often get
ernor,
> ram speed, drive performance/schedulers. Perhaps additional checks like cpu
> bench, fio will not hurt.
> Also disable java security manager.
>
>
> чт, 23 мая 2024 г., 18:24 elisabeth benoit :
>
> > Hello,
> >
> > We've just migrated one of our
Hello,
We've just migrated one of our services from solr 7.3.1 to solr 9.2.1 in
production.
We have 6 servers, each with one solr instance, all conf is automated with
puppet, git, etc. so they all have same conf, but they dont behave the
same way. We have two servers with solr response time much
For the record, I solved this problem by removing stop words in my analyzer
for wordfield.
We often get this problem where there is stop words discrepancies between
fields.
Le jeu. 16 nov. 2023 à 09:28, elisabeth benoit
a écrit :
>
> Thanks a lot for taking time to answer.
>
>
Hello,
Yes we used firstSearcher in solr7. I should have mentionned that we tried
firstSearcher and newSearcher in solr 9, we tried all possibilities we
could think of in solrconfig.xml
Thanks for your answer.
We'll stick to our solution, ie load values in constructor.
Best regards,
Elisabeth
t; during SolrCore init -- and should recieve the args specified in
> solrconfig.xml -- and the parse() will be called each time it is needed.
> If you need information about the SolrIndexSearcher at parse time, you can
> get it from the FunctionQParser (argument) via getReq().getSearcher(
Hello,
We have a solr plugin with parameters in solrconfig.xml.
In the plugin, we use the newSearcher function of a class overriding
AbstractSolrEventListener
to read parameters written in solrconfig.xml.
The plugin is working fine but the plugin function newSearcher is not
called, so we cant
Hello,
We have a solr plugin with parameters in solrconfig.xml.
In the plugin, we use the newSearcher function of a class overriding
AbstractSolrEventListener
to read parameters written in solrconfig.xml.
The plugin is working fine but the plugin function newSearcher is not
called, so we cant
> Best regards,
> > Annika
> >
> >
> >
> > On Thu, Mar 7, 2024 at 12:56 PM atin janki wrote:
> >
> >> Hi Annika,
> >>
> >> Can you please share a sample query and how it is being expanded.
> >> Also, share how you
Hello Annika,
For multiwords synonyms, we have been using
https://github.com/healthonnet/hon-lucene-synonyms jar, that we just
rebuild with solr 9.2.1 (a modification is needed, if you ever need
details).
It overrides edismax query parser and expands multiwords synonyms at query
time.
We didnt w
parser.html#TheDisMaxQueryParser-Themm_MinimumShouldMatch_Parameter
> or experiment with mm.autoRelax=true
>
> https://solr.apache.org/guide/6_6/the-extended-dismax-query-parser.html#TheExtendedDisMaxQueryParser-Themm.autoRelaxParameter
>
>
> On Mon, Nov 13, 2023 at 10:33 PM elisa
ocs: {wordfield:musee, edgefield:musee} as well as {
> wordfield:musee,edgefield:maillol}, {wordfield:musee}, {
> edgefield:maillol}.
> This explanation might be useful
> https://lucidworks.com/post/solr-boolean-operators/
> Note: DisMax works like OR/| but takes max instead of sum
er sums. The good news is that
> the difference between two approaches is only scoring.
> WDYM exactly by absence of "matching words to be in two different fields"?
>
> On Mon, Nov 13, 2023 at 5:01 PM elisabeth benoit <
> elisaelisael...@gmail.com>
> wrote:
>
&
Hello,
I am using solr 7.3.1 with ExtendedDismaxQParser.
I have a edgengrams field and a normal text field. When I mix those two in
the same query, ie *qf=edgefield wordfield* and use option *debugQuery=on*,
I see that the parsedQuery is different, ie all words should match the same
field.
ie pa
result;
}
Best regards
Le mar. 24 oct. 2023 à 17:06, Mikhail Khludnev a écrit :
> I suppose a test may bypass some configs or stages.
> I think the default config shipped with distro has a listener configured
> and we can see that it works in bootstrap logs.
>
> On Tue, Oct 24, 2023
I forgot to add we have this line in solrconfig
Le mar. 24 oct. 2023 à 14:04, elisabeth benoit
a écrit :
>
> Hello,
>
> We have a solr custom plugin that we are actually migrating from solr
> 7.3.1 to solr 9.2.1.
>
> In our solrconfig.xml we have the followi
Hello,
We have a solr custom plugin that we are actually migrating from solr 7.3.1
to solr 9.2.1.
In our solrconfig.xml we have the following line:
The values stopwords and startswith are defined in solrconfig and we read
those values in the newSearcher function of a class implementing
SolrEv
Hello,
I merged two optimized core with solr 7.3.1 with the command
http://localhost:8983/solr/admin/cores?action=mergeindexes&core=result&srcCore=core1&srcCore=core2
First core is 8.41 G, second core is 4.67 G, both are optimized. they have
exactly same schema.xml.
The result core is 22G wi
19 matches
Mail list logo
