defType=edismax is what we have historically used in our application. We’re only trying to use the JSON query DSL for one feature (an advanced search form), and are planning to continue using edismax for all the rest.
-Jane From: David Smiley <david.w.smi...@gmail.com> Date: Monday, July 31, 2023 at 8:53 PM To: users@solr.apache.org <users@solr.apache.org> Subject: Re: JSON boolean query syntax with edismax as default QueryParser Why did you set defType=edismax in the /query handler in your solrconfig.xml? edismax is for handling user queries -- text directly from a text box. JSON Query DSL obviously isn't that. ~ David On Mon, Jul 31, 2023 at 3:09 PM Jane Sandberg <js7...@princeton.edu> wrote: > Hi David, > > Thanks for looking into this, and for the security fix. > > My colleague and I put together a small repository to reproduce the > issue. It has a configset, a docker-compose file, and a README with the > steps to reproduce it on solr 8.4: > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpulibrary%2Fedismax-json-queries%2F&data=05%7C01%7Cjs7389%40princeton.edu%7Ca1e1def2ec954f95453d08db9242ca76%7C2ff601167431425db5af077d7791bda4%7C0%7C0%7C638264587808266610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9FoEGhqSWWk0PefmFFWzY%2Bd4bBN9sDSRtqHQa3DTlx4%3D&reserved=0<https://github.com/pulibrary/edismax-json-queries/> > > Appreciatively, > > -Jane > > From: David Smiley <david.w.smi...@gmail.com> > Date: Monday, July 31, 2023 at 5:58 AM > To: users@solr.apache.org <users@solr.apache.org> > Subject: Re: JSON boolean query syntax with edismax as default QueryParser > Hi Jane, > > That change in 7.2 does look like it's correlated, and I'm the one who > implemented it in the name of security. > > Could you walk me through a short series of steps to show the problem with > one of Solr's "example" setups like techproducts? Step one is run it, step > two is you sending the query via curl. Use whatever Solr version you want. > > ~ David > > > On Fri, Jul 28, 2023 at 10:33 AM Jane Sandberg <js7...@princeton.edu> > wrote: > > > Hi Solr colleagues, > > > > On Solr 8.4.1, we’ve noticed that the following types of JSON DSL queries > > work if our luceneMatchVersion is 7.1 or lower, or if our default query > > parser is set to lucene: > > > > > > > {"query":{"bool":{"must":[{"lucene":{"query":"plasticity","df":"title_a_index"}}]}}} > > > > However, if the query parser is set to edismax and the luceneMatchVersion > > is 7.2 or higher, the parsed query visible with debug=true becomes a > > complete mess, searching for the terms “bool” and “must”, rather than the > > terms we actually want to search for: > > > > > > +(DisjunctionMaxQuery(((author_main_unstem_search:bool)^1000.0 | > > (local_subject_unstem_search:bool)^15.0 | > (author_unstem_search:bool)^40.0 > > […] > > > > Also while debug=true, we noticed that the JSON DSL queries get converted > > into a querystring with local params: ”{!bool must=$_tt1 }”. So I am > > suspecting these two changes in Solr 7.2 as the reason we can’t use > Boolean > > JSON queries with edismax and a recent luceneMatchVersion: > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsolr.apache.org%2Fdocs%2F7_2_0%2Fchanges%2FChanges.html%23v7.2.0.upgrade_notes&data=05%7C01%7Cjs7389%40princeton.edu%7Ca1e1def2ec954f95453d08db9242ca76%7C2ff601167431425db5af077d7791bda4%7C0%7C0%7C638264587808266610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hMGAIWHtYmDP3Ma0huLryFW5AapvfVEMVUYP0b118jQ%3D&reserved=0<https://solr.apache.org/docs/7_2_0/changes/Changes.html#v7.2.0.upgrade_notes> > < > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsolr.apache.org%2Fdocs%2F7_2_0%2Fchanges%2FChanges.html%23v7.2.0.upgrade_notes&data=05%7C01%7Cjs7389%40princeton.edu%7Ca1e1def2ec954f95453d08db9242ca76%7C2ff601167431425db5af077d7791bda4%7C0%7C0%7C638264587808266610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hMGAIWHtYmDP3Ma0huLryFW5AapvfVEMVUYP0b118jQ%3D&reserved=0<https://solr.apache.org/docs/7_2_0/changes/Changes.html#v7.2.0.upgrade_notes> > >. > > Does that seem correct? > > > > Also, could this be related to the question Benjamin Armintor asked on > > June 23 (subject: Changes to JSON query API/syntax in Solr 9.x?)? I’m > > specifically curious about whether a luceneMatchVersion of 7.1 or lower > > still works in Solr 9? > > > > Thanks for your insights, > > > > -Jane > > > > -- > > Jane Sandberg (she/her) > > Library Software Engineer, Discovery and Access Services > > >
