Going to back to the initial question, the wording is a little ambiguous and it occurs to me that it's possible there's a misunderstanding of what autoGeneratePhraseQueries does. It really only auto-generates phrase *subqueries*. To use the example from the initial request, a query like (black company) would always generate a non-phrase query (respecting mm, q.op, etc. -- but in any case not a top-level phrase query), regardless of the setting of autoGeneratePhraseQueries.
autoGeneratePhraseQueries (when set to true) only kicks in (in different ways depending on analysis chain, and setting of "sow") for a query like (the black-company manufactures), which would be transformed to something more like (the "black company" manufactures). The idea is that there's some extra indication that the two words should be bundled together for purposes of querying. If you want to auto-generate a top-level phrase query, some other approach would be called for. Apologies if this is obvious and/or not helpful, Shubham! On Wed, Oct 16, 2019 at 10:10 AM Shawn Heisey <apa...@elyograg.org> wrote: > On 10/16/2019 7:14 AM, Shubham Goswami wrote: > > I have implemented the sow=false property with eDismax Query parser but > > still it does not has any effect > > on the query as it is still parsing as separate terms instead of phrased > > one. > > We have seen reports that when sow=false, which is the default setting > since Solr 7.0, autoGeneratePhraseQueries does not work. Try setting > sow=true and see whether you get the results you expect. > > I do not know whether this behavior is a bug or if it is expected. > > Thanks, > Shawn >
