Re: How to debug empty ParsedQuery from Edismax Query Parser

2019-01-04 Thread Kay Wrobel
I'd like to follow up on this post here because it has become relevant to me now. I have set up a debugging environment and took a deep-dive into the SOLR 7.6.0 source code with Eclipse as my IDE of choice for this task. I have isolated the exact line as to where things fall apart for my two sa

Re: How to debug empty ParsedQuery from Edismax Query Parser

2019-01-02 Thread Kay Wrobel
Thanks for your thoughts, Shawn. Are you a developer on SOLR? Anyway, the configuration (solrconfig.xml) was provided by search_api_solr (Drupal 7 module) and is untouched. You can find it here: https://cgit.drupalcode.org/search_api_solr/tree/solr-conf/7.x/solrconfig.xml?h=7.x-1.x Thank you for

Re: How to debug empty ParsedQuery from Edismax Query Parser

2019-01-02 Thread Shawn Heisey
On 12/28/2018 8:57 AM, Kay Wrobel wrote: Here are my log entries: SOLR 7.x (non-working) 2018-12-28 15:36:32.786 INFO (qtp1769193365-20) [ x:collection1] o.a.s.c.S.Request [collection1] webapp=/solr path=/select params={q=ac6023*&qf=tm_field_product^21.0&qf=tm_title_field^8.0&EchoParams=al

Re: How to debug empty ParsedQuery from Edismax Query Parser

2019-01-02 Thread Kay Wrobel
Well, I was putting that info out there because I am literally hunting down this issue without any guidance. The real problem for still is that the Edismax Query Parser behaves abnormally starting with Version 5 until current giving me empty parsedQuery. Forcing the request through the Lucene pa

Re: How to debug empty ParsedQuery from Edismax Query Parser

2019-01-02 Thread Gus Heck
If you mean attach a debugger, solr is just like any other java program. Pass in the standard java options at start up to have it listen or connect as usual. The port is just a TCP port so ssh tunneling the debugger port can bridge the gap with a remote machine (or a vpn). That said the prior thre

Re: How to debug empty ParsedQuery from Edismax Query Parser

2019-01-02 Thread Kay Wrobel
Is there any way I can debug the parser? Especially, the edismax parser which does *not* raise any exception but produces an empty parsedQuery? Please, if anyone can help. I feel very lost and without guidance, and Google search has not provided me with any help at all. > On Dec 28, 2018, at 9:

Re: How to debug empty ParsedQuery from Edismax Query Parser

2018-12-28 Thread Kay Wrobel
Here are my log entries: SOLR 7.x (non-working) 2018-12-28 15:36:32.786 INFO (qtp1769193365-20) [ x:collection1] o.a.s.c.S.Request [collection1] webapp=/solr path=/select params={q=ac6023*&qf=tm_field_product^21.0&qf=tm_title_field^8.0&EchoParams=all&rows=10&wt=xml&debugQuery=true} hits=0 s

Re: How to debug empty ParsedQuery from Edismax Query Parser

2018-12-27 Thread Alexandre Rafalovitch
EchoParams=all May also be helpful to pinpoint differences in params from all sources, including request handler defaults. Regards, Alex On Thu, Dec 27, 2018, 8:25 PM Shawn Heisey On 12/27/2018 10:47 AM, Kay Wrobel wrote: > > Now starting from SOLR version 5+, I receive zero (0) results bac

Re: How to debug empty ParsedQuery from Edismax Query Parser

2018-12-27 Thread Shawn Heisey
On 12/27/2018 10:47 AM, Kay Wrobel wrote: Now starting from SOLR version 5+, I receive zero (0) results back, but more importantly, the Query Parser produces an empty parsedQuery. Here is the same query issued to SOLR 7.6.0 (current version): https://pastebin.com/XcNhfdUD