lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "none none" <>
Subject Re: New highlighter package available
Date Tue, 30 Sep 2003 20:46:16 GMT
my opinion doesn't count at all! i know that...
but personally i have been pushing for more than a year about highlighting support, i believe
we should compromize a bit.
my opinion is to keep the implementation outside the lucene core (as many of you don't like
it, why??), BUT make the lucene core to support it :)
If you guys want, i can send a document where i explain a few little change to do that (actually
i did already: search mailing for hit collector, is a zip file). 
It is about make a few methods public and add a few arrays to collect terms and a boolean
variable like the one in queryparser: DEFAULT_HIGHLIGHT with values SUPPORTED, NOT_SUPPORTED,
not as default. This is necessary to enable/disable collection of terms when running a search
(same some cpu/memory).
My only reason is to avoid to keep up to date the code everytime there is a major release
or critical updates, because it means to me go through the all code, then run some test cases
to make sure it works properly. And from realease 1.2 to 1.3 was a nice challenge due to very
big changes in the core.
Thank you,

--------- Original Message ---------

DATE: Tue, 30 Sep 2003 14:44:00
From: "Hani Suleiman" <>
To: <>

>Not that my vote counts or is relevant at all, but +1 to not including it,
>for the same reasons below. Let Lucene focus on what it does best, and
>ensure it can support addons and plugins like the highlighter, rather than
>folding them in.
>Otis Gospodnetic said:
>> Couldn't we also stick this in the Sandbox, make sure it builds into a
>> nice little Jar, and just document it in the Lucene's xdocs?
>> I'm just thinking that highlighting is not something that is a
>> necessary feature, so why 'polute' the core that should stay lean as it
>> is today.
>> The same has been done with Snowball code.
>> I don't feel VERY strongly about this, but I do feel that not including
>> it in the core would be a better thing to do.  Those who need it will
>> know how to get the highlighting jar and put it in their CLASSPATH.
>> Otis
>> --- Erik Hatcher <> wrote:
>>> This looks great.
>>> Is everything cool licensing-wise with accepting this?  Is it being
>>> offered to us to be included?
>>> Just a quick glance at the code and the only thing I'd change is the
>>> default hilighting pre/post strings to be <b>/</b>, or perhaps even
>>> something even more general like <em>/</em> or <span
>>> class="hilighted">/</span> - but that is obviously just icing.
>>> 	Erik
>>> On Wednesday, September 24, 2003, at 05:56  PM, Doug Cutting wrote:
>>> > Should this be added into the Lucene core?  I suspect lots of folks
>>> > would like to use something like this.
>>> >
>>> > Doug
>>> >
>>> > wrote:
>>> >> Details of a new highlighter package are available here:
>>> >>
>>> >> Features include:
>>> >> * Support for highlighting all query types
>>> >> * Support for getting "best fragments" summary from large docs *
>>> Works with latest version of Lucene
>>> >> Hope you find this useful.
>>> >> Mark Harwood
>>> >
>>> >
>>> >
>>> ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail:
>>> For additional commands, e-mail:
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: For
>>> additional commands, e-mail:
>> __________________________________
>> Do you Yahoo!?
>> The New Yahoo! Shopping - with improved product search
>> --------------------------------------------------------------------- To
>> unsubscribe, e-mail:
>> For additional commands, e-mail:
>To unsubscribe, e-mail:
>For additional commands, e-mail:

Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!

View raw message