[Dev] Lucene search

Brett Wooldridge bwooldridge at alterpoint.com
Wed Sep 12 20:59:02 CDT 2007


Highlighting is possible.  But maybe not possible in 2007.09.  Lucene
provides a Highlighter framework, and some default implementations ‹ like an
HTML highlighter.  However, since we don¹t display configs as HTML this
would be of little use.  However, the framework is there for us to wire up
our own highlighter logic, which presumably would record byte-offset
start/end highlight pairs or some such.  It is possible that Lucene already
has this, but a quick inspection did not turn it up.

So short answer: yes, possible (and supported) with Lucene.

-Brett


On 9/12/07 8:19 PM, "Ryan Kruse" <rkruse at alterpoint.com> wrote:

> Brett/Leo, 
> 
> Can it be set up so that your search returns the points in the file that match
> so that the client editor that shows the file can highlight (and allow
> clickable 'next' arrows) through the matches just like the eclipse file
> search?
> 
> -Ryan 
> 
> 
> -----Original Message-----
> From: dev-bounces at ziptie.org on behalf of Brett Wooldridge
> Sent: Wed 9/12/2007 7:25 PM
> To: ZipTie Development List
> Subject: [Dev] Lucene search
>  
> Leo, 
> The full text search is 'wired' on the server-side ... I can see that it
> appears to successfully index new configs and to update the index for changed
> configs.  However, I have not tested the actual search.  I intend to write a
> unit test for this, but right now a better use of my time is moving on to the
> server-side script tool execution component.  When you get a chance to wire up
> the front-end to search, let me know.  The query syntax follows this document:
> 
> http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/javadoc/index.ht
> ml 
> 
> We're using their "free form" query syntax parser.  I'm sure we will need to
> make adjustments in both the Analyzer that we use to tokenize the config. file
> as well as the additional fields that we index.  We can also had APIs that
> provide us with more structured searches against the index, for example to
> better enable date range queries.  While some of these "advanced" queries can
> be formed using the free form syntax, providing a simpler UI whereby they user
> selects a date range and enters search text may prove more usable.
> 
> -Brett 
> 
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ziptie.org/pipermail/dev/attachments/20070912/7deace12/attachment.html 


More information about the Dev mailing list