Re: Search returning unexpected matches at the top

I did the following query with debug=results turned on to get an explanation about why owl-2924-8 does not float to the top of the search results. I'm not good at parsing it all, but it appears that it's doing what we expected, in that it's treating the - like a word boundary and matching owl, the

Re: Search returning unexpected matches at the top

On Tue, Dec 10, 2019 at 12:35 AM Paras Lehana wrote: > That's great. > > But I also wanted to know why the concerned document was scored lower in > the original query. Anyways, glad that the issue is resolved. :) > > That I need to look into. If I find an answer, I will let you know. Thanks, Rh

Re: Search returning unexpected matches at the top

That's great. But I also wanted to know why the concerned document was scored lower in the original query. Anyways, glad that the issue is resolved. :) On Tue, 10 Dec 2019 at 00:38, rhys J wrote: > On Mon, Dec 9, 2019 at 12:06 AM Paras Lehana > wrote: > > > Hi Rhys, > > > > Use Solr Query Debu

Re: Search returning unexpected matches at the top

On Mon, Dec 9, 2019 at 12:06 AM Paras Lehana wrote: > Hi Rhys, > > Use Solr Query Debugger > < > https://chrome.google.com/webstore/detail/solr-query-debugger/gmpkeiamnmccifccnbfljffkcnacmmdl?hl=en > > > Chrome > Extension to see what's making up the score for both of them. I guess > fieldNorm sh

Re: Search returning unexpected matches at the top

Hi Rhys, Use Solr Query Debugger Chrome Extension to see what's making up the score for both of them. I guess fieldNorm should impact but that should not be the only thing - there's another catch

Re: Search returning unexpected matches at the top

Please look at the admin UI>>collection_or_core>>analysis page. That will tell you exactly how your input is being transformed. Very often WordDelimiter(Graph)FilterFactory is what breaks data up like this, that’s what it’s _designed_ for. Best, Erick > On Dec 6, 2019, at 11:25 AM, rhys J wro

Re: Search returning unexpected matches at the top

On Fri, Dec 6, 2019 at 11:21 AM David Hastings wrote: > whats the field type for: > clt_ref_no > It is a text_general field because it can have numbers or alphanumeric characters. *_no isnt a default dynamic character, and owl-2924-8 usually translates > into > owl 2924 8 > > So it's matching o

Re: Search returning unexpected matches at the top

.com/contact-us From: Alexandre Rafalovitch Sent: Friday, December 6, 2019 11:15 AM To: solr-user Subject: Re: Search returning unexpected matches at the top You can enable debug which will show you what matches and why. Check the reference guide for parame

Re: Search returning unexpected matches at the top

You can enable debug which will show you what matches and why. Check the reference guide for parameters: https://lucene.apache.org/solr/guide/8_1/common-query-parameters.html#debug-parameter Regards, Alex. On Fri, 6 Dec 2019 at 11:00, rhys J wrote: > > I have a search box that is just searchi

Search returning unexpected matches at the top

I have a search box that is just searching every possible core, and every possible field. When I enter 'owl-2924-8', I expect the clt_ref_no of OWL-2924-8 to float to the top, however it is the third result in my list. Here is the code from the search: on_data({ "responseHeader":{ "status"