lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35518] - Alternate Lucene Query Parser
Date Tue, 28 Jun 2005 07:21:00 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35518>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35518





------- Additional Comments From paul.elschot@xs4all.nl  2005-06-28 09:20 -------
(In reply to comment #3) 
... 
> Going forward I think it would be useful to try retain some of the features 
of 
> the existing highlighter (eg IDF weighted fragment scoring, fragSizes defined 
> in bytes) and merge with your phrase-highlighting features.Adding span query 
> support would be good too. What I'm less clear on right now is how this is 
best 
> achieved. 
 
Given the possibility of nested span queries, it might be best 
do this is by reindexing the field to be highlighted in ram, reuse 
the span query on it for collecting the Spans (via getSpans()) 
and use the beginnings and the ends from this spans as 
the basis for highlighting. 
For efficiency during reindexing the analyzer used to assemble 
the lucene document could ignore all tokens that will not match, 
except for their positions. 
 
Regards, 
Paul Elschot 
 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message