Apr
1
2008
1
2008
Hit Highlighting with Searchable
The latest snapshot of the Grails Searchable Plugin now has hit highlighting. I’ve been waiting on this feature, and it’s good to go. With some help from the list, I’ve now got it up and running on Gravl. Here’s the results so far:
So, how much work is it to implement? Coupla lines…inside my seach method, I just need to add a withHighlighter closure into the mix and I was off:
params.withHighlighter = { highlighter, index, sr ->
// lazy-init the storage
if (!sr.highlights) {
sr.highlights = []
}
// store highlighted text; "body" is a searchable-property of the BlogEntry domain class
def matchedFragment = highlighter.fragment("body")
sr.highlights[index] = "..." + (matchedFragment ?: "") + "..."
}
// limit query to current blog published entries...
def results = BlogEntry.search(query, params)
Then, in the view, spit out the fragment and I’m done…
<p class='hitBody'>
${ results.highlights[i] }
</p>
There still a bit of work to do, for bonus marks:
- I really need to implement highlighting on the title too, if it search term matches in there.
- It would also be good to store the blog content stripped of html in the index so that markup of hit terms doesn’t include any of the original markup
- Finally, it would be nice to include multiple highlights of terms for each hit (eg “..entry about gravl… and later in the para about gravl or … and later still about gravl…”). Lucene lets you configure this, so there’s probably a way to do it for Compass, too.
Props to Maurice for a great new feature! Searchable highlighting rocks!
3 Comments + Add Comment
Leave a comment
Glen Smith
Archives
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- January 2011
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003

An article by Glen





Thanks for the blog entry Glen… and for making Gravl open for contributions. I do hope to find some time to contribute.
And good work on the podcast as well!
Hey Glen,
another great article!
You could achieve #1 and #3 from your todos with multiple calls to the highlighter in the closure, eg:
withHighlighter: { highlighter, index, sr ->
// … create/obtain a “highlights” array to store highlights
highlights[index] = [
title: highlighter.fragment("title"),
body: highlighter.fragmentsWithSeparator("body")
]
}
Check out the CompassHighlighter API at http://www.compass-project.org/docs/1.2.1/api/org/compass/core/CompassHighlighter.html
Also #2 isn’t that hard: it should be a case of defining a read-only property, something like:
class BlogEntry {
// …
String getContentTextOnly() {
// return the content markup-free
}
}
then “contentTextOnly” should available as a searchable property, so you could highlight its text like regular domain class properties. I haven’t tested this last bit but it *should* work
Cheers
Thanks Maurice. That’s awesome news. I’ll give it a crack.