lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Naomi Dushay <>
Subject autoGeneratePhraseQueries sort of silently set to false
Date Thu, 23 Feb 2012 18:56:39 GMT
Another thing I noticed when upgrading from Solr 1.4 to Solr 3.5 had to do with results when
there were hyphenated words:   aaa-bbb.   Erik Hatcher pointed me to the autoGeneratePhraseQueries
attribute now available on fieldtype definitions in schema.xml.  This is a great feature,
and everything is peachy if you start with Solr 3.4.   But many of us started earlier and
are upgrading, and that's a different story.

It was surprising to me that

a.  the default for this new feature caused different search results than Solr 1.4 

b.  it wasn't documented clearly, IMO   makes no mention of it

In the schema.xml example, there is this at the top:

<!-- attribute "name" is the name of this schema and is only used for display purposes.
       Applications should change this to reflect the nature of the search collection.
       version="1.4" is Solr's version number for the schema syntax and semantics.  It should
       not normally be changed by applications.
       1.0: multiValued attribute did not exist, all fields are multiValued by nature
       1.1: multiValued attribute introduced, false by default 
       1.2: omitTermFreqAndPositions attribute introduced, true by default except for text
       1.3: removed optional field compress feature
       1.4: default auto-phrase (QueryParser feature) to off

And there was this in a couple of field definitions:

<fieldType name="text_en_splitting" class="solr.TextField" positionIncrementGap="100" autoGeneratePhraseQueries="true">
<fieldType name="text_ja" class="solr.TextField" positionIncrementGap="100" autoGeneratePhraseQueries="false">

But that was it.

View raw message