Same here. "sow" restores the old behavior. The schema.xml in both Solr versions for me is the one that gets copied from the default template folder to the collections's conf folder. On 7 though, looks like the schema changes file changes to "managed-schema".
The fieldtype that corresponds to field "contents" is "text", and the definition of "text" field in 5 and the schema backup on 7 is the same. On 7 Solr backs up the original schema.xml and creates a managed schema config file. I tried the analysis tab. Looks like all the classes (WT, SF ...) in 7 list a property (termFrequency = 1) that is missing in 5. Lemme see if I can share the schemas. -----Original Message----- From: David Hastings [mailto:hastings.recurs...@gmail.com] Sent: Thursday, May 10, 2018 1:38 AM To: solr-user@lucene.apache.org Subject: Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7. sow=true made 7 mimic 5. On Wed, May 9, 2018 at 3:57 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 5/9/2018 1:25 PM, David Hastings wrote: > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpas > > tebin.com%2F0QUseqrN&data=02%7C01%7Cpnayak%40adobe.com%7C2f18f520a2f > > b463faabf08d5b5e89166%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6 > > 36614932828978588&sdata=gs9zG65%2FMZayaIthXJZSbE6m%2FvjKd2uBPnRIta98 > > Haw%3D&reserved=0 > > > > here is mine for an example with the exact same behavior > > Can you try the query in the Analysis tab in the admin UI on both > versions and see which step in the analysis chain is the point at > which the two diverge from each other? > > I would still like to see the full schema, but I have an idea for a > troubleshooting step. Can you add "sow=true" to the URL on version 7 > and see if that makes any difference? The query that the OP is using > doesn't have spaces, but there might be some kind of odd interaction > between sow and other settings. I believe the default value for sow > changed to false in version 7. > > You also might try setting autoGeneratePhraseQueries to false on the > fieldType, which might cause version 5 to behave the same as 7. But > be warned that this could make things work very differently than users > might expect. > > Thanks, > Shawn >
