By default, MLT uses the top 25 terms from the target document to do
similarity searches. A quick look at the source code (
https://github.com/apache/lucene-solr/blob/master/lucene/queries/src/java/org/apache/lucene/queries/mlt/MoreLikeThis.java
) and Lucene documentation (
https://lucene.apache.or
As a side note, if you use shingles with the mlt handler I believe you will get
better scores/relevant results. So “to be free” becomes indexes as “to_be”
“to_be_free” and “be_free” but also as each word. It makes the index
significantly larger but creates better “unique terms” in my opinion and
Thank you very much for quick response. This is very much helpful to us.
While analyzing the results for some jobs, it is returning high score for
a document which is not much relevant to the base document.
Is there any way we can improve the results and scoring?
How it exactly give the score fo
I only copied the 2 jars
-
jwt-auth-1.0.0.jar
-
jose4j-0.6.3.jar
to the $SOLR_HOME/lib folder, to install the code for the
https://github.com/cominvent/solr-auth-jwt plugin
On Fri, Sep 13, 2019 at 11:55 AM Shawn Heisey wrote:
> On 9/13/2019 10:30 AM, Tyrone Tse wrote:
> > When
It would help if you could devise a simple set of command line steps to
reproduce/demonstrate the problem using the "bin/solr -e solrcloud" setup.
The problem you see ought to be reproducible here if there is a problem.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/
On 9/13/2019 10:30 AM, Tyrone Tse wrote:
When I check the solr.log file I am seeing the following error
2019-09-13 15:09:27.816 ERROR (main) [ ] o.a.s.s.SolrDispatchFilter Could
not start Solr. Check solr/home property and the logs
2019-09-13 15:09:27.838 ERROR (main) [ ] o.a.s.c.SolrCore
nu
I am testing the JWT Auth plugin from
https://github.com/cominvent/solr-auth-jwt
as my project is using Solr 7.2.
I downloaded the master branch for the code, and I built the
jwt-auth-1.0.0.jar
with the mvn package command.
I then copied the jar to my $SOLR_HOME/lib/
I also downloaded the jose4
To use knnSearch, you need to submit a POST request to the Stream request
handler.
Using your example query, you will need to rewrite them from this :
*http://[SOLR*
URL]/mlt?q=sjkey:1414462-25600-5258&wt=json&indent=true&mlt=true&rows=100&mlt.fl=jobdescription&mlt.mindf=1&mlt.mintf=1&fl=jobtitle
Hi Chee Yee Lim,
Thank you for your quick response.
We do not find much documentation on knnsearch on how to do use that.
Could you please guide us with more info on how this can be used?
Can we use this the way we use Solr by querying with Solr URL like
http://[SOLR URL]/mlt ? OR any ot
Hi Akreeti,
How much should I set "commitReserveDuration" for 2.62 GB ?
That's why I asked you about the time taken by the replication. You can
easily get hint about it after manually starting replication. The
commitReserveDuration should be roughly set as the time taken to download
5MB from mas
Hi,
I have no idea about how much time is taken for successful replication for 2.62
GB. How much should I set "commitReserveDuration" for 2.62 GB ?
Thanks & Regards,
Akreeti Agarwal
-Original Message-
From: Paras Lehana
Sent: Thursday, September 12, 2019 6:46 PM
To: solr-user@lucene.a
11 matches
Mail list logo
