Re: Why does edismax resets field level wild query to *:*

2023-11-15 Thread rajani m
Thank you, Hoss. That answered my question. On Wed, Nov 15, 2023, 1:08 PM Chris Hostetter wrote: > > : Why does edismax query reset field exist query to *:*? Is this > : expected behavior or a bug? > : > : Edismax query "q": "{!edismax qf=keywords v='*'}" or in the other > : form "q=*&qf=

Re: Why does edismax resets field level wild query to *:*

2023-11-15 Thread Chris Hostetter
: Why does edismax query reset field exist query to *:*? Is this : expected behavior or a bug? : : Edismax query "q": "{!edismax qf=keywords v='*'}" or in the other : form "q=*&qf=keywords.en&defType=edismax" : I expected this to translate into keywords:* this is an intentional feature o

Re: Why does edismax resets field level wild query to *:*

2023-11-15 Thread rajani m
Hi Vaijanath, qf is *not* set to star but the field name "keywords". It is the value that is set to star "q": "{!edismax qf=keywords v='*'}" On Wed, Nov 15, 2023 at 10:19 AM Vaijanath Rao wrote: > As far as I can recall/remember this is an expected behavior. The value for > the query is coming

Re: Why does edismax resets field level wild query to *:*

2023-11-15 Thread Vaijanath Rao
As far as I can recall/remember this is an expected behavior. The value for the query is coming from the parameter v and qf is coming from the parameter qf which in this example is set to "*". Hence q=* and qf = keywords.en. --Thanks and regards Vaijanath On Wed, Nov 15, 2023 at 7:06 AM rajani m