Mike Klaas wrote:
I think there might be value in providing less explicit Highlighter configuration and instead provide a set of intuitive options form which we can construct various configurations. For another point of configuration is the Scorer -- right now the default QueryScorer is used. But you can also specify an IndexReader+fieldName to the QueryScorer constructor to augment fragment scores with IDF values for the terms, which is necessary to see a difference in Gradient formatting. It would be nice to hide all those details from the user.
Well, that explains why I wasn't getting any variations when using the gradient formatter. Also, creating the QueryScorer with the fieldName prevents highlights from appearing where they shouldn't - e.g. when searching for +title:management +journal:quarterly I was seeing "Management" highlighted in my journal field as well as the title.
Is there much of an extra cost in using a scorer created with the IndexReader and fieldName? -Andrew
