OK - I understand your point.
However - I believe that it can be both effective and useful, depending on
the nature of the application and the users.
If the usual hl parameters to enable snippet highlighting for MLT
interesting terms were available, you would have the choice to enable,
disable
wrote:
Any luck on this? I am experiencing the same issue. Highlighting
works fine on all other request handlers, but breaks when I use the
MoreLikeThisHandler.
Thanks,
Matt Weber
On Apr 28, 2009, at 5:29 AM, Eric Sabourin wrote:
Yes... at least I think so
Yes, I understand you can't highlight a documented within a document.
However, with MLT you a using the interesting terms from the source
document(s) to find similar results. An obvious solution would be
highlighting the interesting terms that matched and thus made the
result similar
http://wiki.apache.org/solr/HighlightingParameters
I can specify the strings to highlight matched text with using
hl.simple.pre and hl.simple.post, for example b and /b.
The result looks like this:
strlt;bgt;Eumellt;/bgt; NDR Ländermagazine/str
However, what if as the result of favouring XML
Hi Matt,
On Tue, Apr 28, 2009 at 4:24 AM, Matt Mitchell goodie...@gmail.com wrote:
I've been toying with setting custom pre/post delimiters and then removing
them in the client, but I thought I'd ask the list before I go to far with
that idea :)
this is what I do. I define the custom
Yes... at least I think so. the highlighting works correctly for me on
another request handler... see below the request handler for my
morelikethishandler query.
Thanks for your help... Eric
requestHandler name=/mlt class=solr.MoreLikeThisHandler
lst name=defaults
str name=fl
Hi Christian,
I decided to do something very similar. How do you handle cases where the
highlighting is inside of html/xml tags though? I'm getting stuff like this:
?q=jackson
entry type=song author=Michael emJackson/emBad by Michael
emJackson/em/entry
I wrote a regular expression to take care
Hi,
I've been looking around but can't seem to find any clear instruction on how
to do this... I'm storing html content and would like to enable highlighting
on the html content. The problem is that the search can sometimes match html
element names or attributes, and when the highlighter adds
Sent: Monday, April 27, 2009 10:31:38 AM
Subject: Term highlighting with MoreLikeThisHandler?
I submit a query to the MoreLikeThisHandler to find documents similar to a
specified document. This works and I've configured my request handler to
also return the interesting terms
because of many solved enterprise features. I have to say It
is great project! I've downloaded Solr 1.3 + SolrJ and have tried to
use as embedded one. Everything works fine but one thing is missing -
or I can not find it.
In pure Lucene, I can do highlighting after searching. Field values
Does Solr support highlighting for wildcard searches?. Like I search for
tele* and all words matching 'tele' should get highlighted ex:
telephone, telex etc. I am trying to get the highlighting using
ressponse.getHighlighting(). But It returns empty list. Would appreciate
any help.
Thanks.
On Mon, Mar 16, 2009 at 7:27 PM, Narayanan, Karthikeyan
karthikeyan.naraya...@gs.com wrote:
Does Solr support highlighting for wildcard searches?. Like I search for
tele* and all words matching 'tele' should get highlighted ex:
telephone, telex etc. I am trying to get the highlighting using
I was wondering if there is any way of highlighting the searched term in the
resultset directly instead of having it as a separate lst element.
Doing it through xsl transformation would be one way.
Has anybody implemented any other better solution ?
e.g
result name=response numFound=293 start
Mark Miller wrote:
Currently I think about dropping the stemming and only use
prefix-search. But as highlighting does not work with a prefix house*
this is a problem for me. The hint to use house?* instead does not
work here.
Thats because wildcard queries are also not highlightable now
(gap) fragmenter with some simple,
single-word queries on a patched 1.3.0 release populated with some
real-world data. (I think the primary quirk in my setup is that I'm
using ShingleFilterFactory to put word bigrams (aka shingles) into my
index. I was worried that this might mess up highlighting
to get highlighting working, with no luck so far.
Query with params
q=cyrusfl=*,scoreqt=standardhl=truehl.fl=title+description
finds 182 documents in my index. All of the top 10 hits contain
the word cyrus, but the highlights list is empty. The fields
title and description are stored
-01-27, o godz. 13:09, przez
Jarek Zgoda:
Solr 1.3
I'm trying to get highlighting working, with no luck so far.
Query with params
q=cyrusfl=*,scoreqt=standardhl=truehl.fl=title+description
finds 182 documents in my index. All of the top 10 hits
contain the word cyrus, but the highlights
I'm trying to get highlighting working, with no luck so far.
Query with params
q=cyrusfl=*,scoreqt=standardhl=truehl.fl=title+description
finds 182 documents in my index. All of the top 10 hits contain
the word cyrus, but the highlights list is empty. The fields
title and description
Solr 1.3
I'm trying to get highlighting working, with no luck so far.
Query with params q=cyrusfl=*,scoreqt=standardhl=truehl.fl=title
+description finds 182 documents in my index. All of the top 10 hits
contain the word cyrus, but the highlights list is empty. The fields
title
I turned these fields to indexed + stored but the results are exactly
the same, no matter if I search in these fields or elsewhere.
Wiadomość napisana w dniu 2009-01-27, o godz. 13:09, przez Jarek Zgoda:
Solr 1.3
I'm trying to get highlighting working, with no luck so far.
Query
, no matter if I search in these fields or elsewhere.
Wiadomość napisana w dniu 2009-01-27, o godz. 13:09, przez Jarek
Zgoda:
Solr 1.3
I'm trying to get highlighting working, with no luck so far.
Query with params q=cyrusfl=*,scoreqt=standardhl=truehl.fl=title
+description finds 182 documents
godz. 13:09, przez Jarek
Zgoda:
Solr 1.3
I'm trying to get highlighting working, with no luck so far.
Query with params
q=cyrusfl=*,scoreqt=standardhl=truehl.fl=title+description
finds 182 documents in my index. All of the top 10 hits contain
the word cyrus, but the highlights list
wrote a highlighter:
https://issues.apache.org/jira/browse/LUCENE-1522
I'm not shingle expert, but my highlighter has some pluggable interfaces,
a plugin may be written to solve your problem.
regards,
Koji
Chris Harris wrote:
I'm running into some highlighting issues that appear to arise only
I'm indexing text from an OCR of an old document. Many words get read
perfectly, but they're typically embedded in a lot of junk. I would
like the hit highlighting to show only the 'good' words, in the order
in which they appeared in the original document. Is it possible to
use output
- Original Message
From: Terence Gannon butzi0...@gmail.com
To: solr-user@lucene.apache.org
Sent: Monday, January 12, 2009 11:00:31 AM
Subject: Improving Readability of Hit Highlighting
I'm indexing text from an OCR of an old document. Many words get read
perfectly, but they're
To answer your questions specifically, here is an example of the raw OCR output;
CONTRACTORINMPRIMENTAYIVE : mom Ale ACCEPT INFORMATIONON TOUR SHEET TO ea
to which I would like to see;
mom ale access tour sheet to
in the hit highlight. My schema for this field is pretty much
standard, as
I'm running into some highlighting issues that appear to arise only
when I'm using a bigram shingle (ShingleFilterFactory) analyzer.
I started with a bigram-free situation along these lines:
field name=body type=noshingleText indexed=false stored=false /
!-- Stored text for use
4:07:57 PM
Subject: Re: Improving Readability of Hit Highlighting
To answer your questions specifically, here is an example of the raw OCR
output;
CONTRACTORINMPRIMENTAYIVE : mom Ale ACCEPT INFORMATIONON TOUR SHEET TO ea
to which I would like to see;
mom ale access tour sheet
Hi,
I cant get highlighting to work. I tried everything mentioned about it on
the forum. PLEASE HELP...
We use solrJ; search a field called content, it is the default search field,
indexed and stored. Its type is text, has analyzer associated with it. There
is no uniqueKey in the schema
. If the user searches for him by author, we get correct
highlighting in the author field, but only Joe and not Bloggs is
highlighted in the main body field. Conversely, if the user searches
for
Joe Bloggs in the main body field, the highlighting is correct in that
field but this time only Joe
by author.
Now, suppose we have an author named Joe Bloggs whose name appears in
both
the fields. If the user searches for him by author, we get correct
highlighting in the author field, but only Joe and not Bloggs is
highlighted in the main body field. Conversely, if the user searches
to avoid
unexpected matches when searching by author.
Now, suppose we have an author named Joe Bloggs whose name appears in both
the fields. If the user searches for him by author, we get correct
highlighting in the author field, but only Joe and not Bloggs is
highlighted in the main body field
an author named Joe Bloggs whose name appears in both
the fields. If the user searches for him by author, we get correct
highlighting in the author field, but only Joe and not Bloggs is
highlighted in the main body field. Conversely, if the user searches for
Joe Bloggs in the main body field
config, enable per-query with hl=true --
str name=hl.fltext features name/str
!-- for this field, we want no fragmenting, just highlighting --
str name=f.name.hl.fragsize0/str
!-- instructs Solr to return the field itself if no query terms are
found --
str name
2lt;-1 5lt;-2 6lt;90%
/str
int name=ps100/int
str name=q.alt*:*/str
!-- example highlighter config, enable per-query with hl=true --
str name=hl.fltext features name/str
!-- for this field, we want no fragmenting, just highlighting --
str name
!-- for this field, we want no fragmenting, just highlighting --
str name=f.name.hl.fragsize0/str
!-- instructs Solr to return the field itself if no query terms are
found --
str name=f.name.hl.alternateFieldname/str
str name=f.text.hl.fragmenterregex/str !-- defined below
Hi,
i'm using solr 1.3.0 and SolrJ for my java application
I need to highlight my query words even if I use wildcards
for example
q=tele*
i need to highlight words as television, telephone, etc
I found this thread
To do it now, you'd have to switch the query parser to using the old
style wildcard (and/or prefix) query, which is slower on large indexes
and has max clause issues.
I think I can make it work out of the box for the next release again
though. see
On 21-Nov-08, at 3:45 AM, Mark Miller wrote:
To do it now, you'd have to switch the query parser to using the old
style wildcard (and/or prefix) query, which is slower on large
indexes and has max clause issues.
An alternative is to query for q=tele?*, which forces wildcardquery
-Mike
that this might mess up highlighting, but
highlighting is *mostly* working.) There are some oddities here, and
I'm wondering if people have any suggestions for debugging my setup
and/or trying to make a good, reproducible test case.
1. The main weird thing is that, the vast majority of the time
Hi Lars,
Thanks for it: it works great.
BR
Christophe
Lars Kotthoff wrote:
I'm doing the following query:
q=text:abc AND type:typeA
And I ask to return highlighting (query.setHighlight(true);). The search
term for field type (typeA) is also highlighted in the text field.
Anyway to avoid
Hi,
I'm doing the following query:
q=text:abc AND type:typeA
And I ask to return highlighting (query.setHighlight(true);). The search
term for field type (typeA) is also highlighted in the text field.
Anyway to avoid this ?
Thanks
Christophe
christophe wrote:
Hi,
I'm doing the following query:
q=text:abc AND type:typeA
And I ask to return highlighting (query.setHighlight(true);). The
search term for field type (typeA) is also highlighted in the text
field.
Anyway to avoid this ?
Thanks
Christophe
I havn't used solrj really
I'm doing the following query:
q=text:abc AND type:typeA
And I ask to return highlighting (query.setHighlight(true);). The search
term for field type (typeA) is also highlighted in the text field.
Anyway to avoid this ?
Use setHighlightRequireFieldMatch(true) on the query object [1].
Lars
Hello.
I enabled highlighting and it works perfect, but not for all queries.
For example if ?q=canon+powershot I get this response:
---
{
responseHeader:{
status:0,
QTime:4},
response:{numFound:296,start:0,maxScore:4.3135004,docs
Researching more, it was already an issue. Sorry for the inconvenience.
http://issues.apache.org/jira/browse/SOLR-42
Pako
Francisco Sanmartin wrote:
Highlighting in Solr has a strange behavior in some items. I attach an
example to see if anyone can throw some light at it. Basically solr
http://wiki.apache.org/solr/FieldOptionsByUseCase says that a field
needs to be both stored and indexed for highlighting to work. Unless
I'm very confused, though, I just tested and highlighting worked fine
(on trunk) for a stored, *non-indexed* field. So is this info perhaps
out of date
On 3-Sep-08, at 1:29 PM, Chris Harris wrote:
http://wiki.apache.org/solr/FieldOptionsByUseCase says that a field
needs to be both stored and indexed for highlighting to work. Unless
I'm very confused, though, I just tested and highlighting worked fine
(on trunk) for a stored, *non-indexed
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: pdovyda2 [EMAIL PROTECTED]
To: solr-user@lucene.apache.org
Sent: Thursday, August 14, 2008 2:56:42 PM
Subject: Highlighting returns incorrect text on some results?
This is kind of a strange
This is kind of a strange issue, but when I submit a query and ask for
highlighting back, sometimes the highlighted text includes a question mark
at the beginning, although a question mark character does not appear in the
field that the highlighted text is taken from.
I've put some sample XML
PM
Subject: Highlighting returns incorrect text on some results?
This is kind of a strange issue, but when I submit a query and ask for
highlighting back, sometimes the highlighted text includes a question mark
at the beginning, although a question mark character does not appear
I tried to post it myself, got the address wrong, thanks for re-posting.
the problem we have with highlighting outside of the indexer is that the
systems we use that store co-ords are... based on term string (in one
case) and the specific term offset in another. Both of which break
horribly when
Martin,
You may want to follow Mark Miller's effort
https://issues.apache.org/jira/browse/LUCENE-1286 as it develops --
perhaps even help with it. He's developing a Lucene highlighter which
would run through query terms by using their offsets making
highlighting large documents much more
Martin,
I've been over some of the same thoughts you present here in the last
few years. The path of least resistance ended up being to deal with the
highlighting portion of OCRed images outside of Solr. That's not to say
it couldn't or shouldn't be done differently. I briefly even pursued
Hi,
I'm using solr built from trunk and highlighting for range queries doesn't
work.
If I search for 2008 everything works as expected but if I search for
[2000 TO 2008] nothing gets highlighted.
The field I'm searching on is a TextField and I've confirmed that the query
and index analyzers
in
global-idf for distributed search).
-Yonik
On Wed, Jun 11, 2008 at 11:09 AM, Stefan Oestreicher
[EMAIL PROTECTED] wrote:
Hi,
I'm using solr built from trunk and highlighting for range queries doesn't
work.
If I search for 2008 everything works as expected but if I search for
[2000 TO 2008
On 5-Jun-08, at 8:31 PM, Kevin Xiao wrote:
Hi,
I have a question about highlighting fragment. I set hl.fragsize to
100, but the return is cut off from a middle of a sentence with
correct search term highlighting though. Is there a way to make the
cutoff to the beginning of a sentence
to contain the text CPR which is not
the case.
Any ideas?
--
View this message in context:
http://www.nabble.com/Highlighting-and-Synonyms-tp17665705p17665705.html
Sent from the Solr - User mailing list archive at Nabble.com.
AM
Subject: Highlighting and Synonyms
I have some data that contains phrases such as
1) Decisions Relating to Cardiopulmonary Resuscitation: Model Information
Leaflet. British Medical Association
2) to ensure that cardiopulmonary resuscitation (CPR) may safely proceed
The data
Hi,
I have a question about highlighting fragment. I set hl.fragsize to 100, but
the return is cut off from a middle of a sentence with correct search term
highlighting though. Is there a way to make the cutoff to the beginning of a
sentence? Set some flag? How does highlighting cutoff work
Hi,
in order to use phrase highlighting I built a war from the current svn
trunk.
(http://www.nabble.com/-jira--Commented:-(SOLR-553)-Highlighter-does-not-mat
ch-phrase-queries-correctly-p17234014.html) It deployed without problems and
the info section in the admin panel correctly (?) reports
Implementation Version: 1.3-dev.
However there's no difference at all if I use
hl.usePhraseHighlighter=true
in my select request, phrase terms are still highlighted individually.
That's a different issue, SOLR-553 was to fix the bug that
highlighting would return snips that did not match
: Brian Whitman [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 02. Juni 2008 15:57
An: solr-user@lucene.apache.org
Betreff: Re: phrase highlighting
On Jun 2, 2008, at 9:51 AM, Stefan Oestreicher wrote:
(http://www.nabble.com/-jira--Commented:-(SOLR-553)-Highlighter-does-n
ot-mat
ch-phrase-queries
Hi,
I've started to play around with Solr and I'm quite impressed with its
performance and features. However it seems to me that highlighting of
wildcard terms is not supported, which is somewhat disappointing. Are there
any plans to support that or did I miss something?
best regards,
Stefan
On 30-May-08, at 6:45 AM, Stefan Oestreicher wrote:
Hi,
I've started to play around with Solr and I'm quite impressed with its
performance and features. However it seems to me that highlighting of
wildcard terms is not supported, which is somewhat disappointing.
Are there
any plans
Hi
I am not sure if there are any discussions about this, I could not find the
search function in mailing list archives. :) Anyway, here is my problem:
In my document, I have a hyperlink, say, a
href=../home/home.nb?q=breast+cancerbreast cancer/a, but when I applied
solr highlighting
cancer/a, but when I applied solr
highlighting on search term 'cancer', that hyperlink becomes: a
href=../home/home.nb?q=breast+span class=TermHighlightcancer/
spanbreast span class=TermHighlightcancer/span/a.
Obviously I don't want highlighting the first cancer (in red).
Is there a flag
TO
20080520]start=0rows=11hl=onhl.fl=body_nlhl.snippets=3hl.fragsize=320hl.simple.pre=stronghl.simple.post=/strongsort=publishdateAsString
desc,publicationname descfl=id,score,introduction
we get nice highlighting from the body_nl field but Solr also highlights 3430
and 3451 if there is such a word
)) )fq= +publishdateAsString:[20070520 TO
20080520
]start
=
0
rows
=
11
hl
=
on
hl
.fl
=
body_nl
hl
.snippets=3hl.fragsize=320hl.simple.pre=stronghl.simple.post=/
strongsort=publishdateAsString desc,publicationname
descfl=id,score,introduction
we get nice highlighting from
, but at
the end of document added:
lst name=highlighting
−lst
−arr name=ABST
−str
-gestational anemia as a consequence of a reduction in the number of primitive
erythroid cells. emGATA/em-em1/em mRNA is
/str
/arr
/lst
…
/lst
The content of ABST of highlighting is much smaller than that of the original.
I am
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 14, 2008 5:55 AM
To: solr-user@lucene.apache.org
Subject: Re: solr highlighting
On Wednesday 14 May 2008 09:21:36 Kevin Xiao wrote:
Hi there,
I am new to solr. I want search term to be highlighted on the results. I
thought it is pretty simple, but could
@lucene.apache.org
Subject: Re: solr highlighting
On Wednesday 14 May 2008 09:21:36 Kevin Xiao wrote:
Hi there,
I am new to solr. I want search term to be highlighted on the
results. I
thought it is pretty simple, but could not make it work. I read a
lot of
solr documents and mail archives (I wish
Koji,
The patch is now available at https://issues.apache.org/jira/browse/SOLR-538
Tell me if it fits your needs.
Nicolas
-Message d'origine-
De : Koji Sekiguchi [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 21 mars 2008 16:50
À : solr-user@lucene.apache.org
Objet : Re: Slow Highlighting
Hello Nicolas,
Thank you for letting me know this.
Yes, your patch will solve my problem (highlighter performance w/ large
doc).
BTW, I posted similar ticket to solve my another problem (hl.alternateField
w/ large field).
https://issues.apache.org/jira/browse/SOLR-516
Thank you again,
Koji
Hi,
Would it be easier if you turn off the highlighting while viewing full
document (but summary highlighting is still available) and use javascript to
do the matching? (As long as we are need highlighting only when looking at
specific document in runtime)
Thank you,
Vinci
Brian Whitman wrote
the same thing. There's a patch in lucene (not
in trunk yet) to support this.
Oh dear, you did ask the same question very recently. Sorry to re-ask
the same thing, everybody.
For the record, that thread is called highlighting pt2: returning
tokens out of order from PhraseQuery, and it's (currently
Objet : Re: Slow Highlighting - CopyField maxSize property
Hello Nocolas,
This has been in the back of my mind for a time.
Can you make a patch for it? I'd like to use it.
Thank you,
Koji
[EMAIL PROTECTED] wrote:
Hi all,
I would like to propose a new property on copy fields that limit
I'm using the standard Solr query language and the normal highlighting
parameters documented at
http://wiki.apache.org/solr/HighlightingParameters. Snippet generation
and highlighting is working pretty well, but my testers have
discovered something they find borderline unacceptable. If they search
On Mar 25, 2008, at 6:31 PM, Chris Harris wrote:
working pretty well, but my testers have
discovered something they find borderline unacceptable. If they search
for
stock market
(with quotes), then Solr correctly returns only documents where
stock and market appear as adjacent words. Two
: A query with highlighting and requireFieldMatch like so:
: .../select?q=%22U2%22hl=truehl.fl=content
: hl.requireFieldMatch=truehl.fragsize=500hl.snippets=5hl.simple.pre=
: %3Cspan%3Ehl.simple.post=%3C/span%3E
:
: does not return highlighting for this document (it is returned as a query
case is the following: Among other documents, we index very big
documents (several Mo of text) and want to be able to use highlighting.
However, as soon as one or more big documents are included in the matches,
the response time is awful. The maxAnalyzedChars is not enough as the full
document
On Mar 19, 2008, at 10:26 AM, Brian Whitman wrote:
Can we somehow force the highlighter to not return snips that do
not exactly match the query?
Unfortunately not with the current highlighter. But there has been a
great deal of work towards fixing this here: http://
Unfortunately not with the current highlighter. But there has been
a great deal of work towards fixing this here: http://issues.apache.org/jira/browse/LUCENE-794
ah, thanks Eric, didn't think to check w/ the lucene folks.
I see they have somewhat working patches -- does this kind of
On Mar 20, 2008, at 4:13 PM, Brian Whitman wrote:
Unfortunately not with the current highlighter. But there has
been a great deal of work towards fixing this here: http://
issues.apache.org/jira/browse/LUCENE-794
ah, thanks Eric, didn't think to check w/ the lucene folks.
I see they
on a solr text fieldtype called content, I have text like the
following:
Bono (L), Irish lead singer of the band U2 and Kurt Beck, chairman of
the German Social Democratic Party (SPD) address the media at the
party?s headquarters in Berlin May 14, 2007.
A query with highlighting
you can see this code arround line
362 of DisMaxRequestHandler.java...
/* * * Highlighting/Summarizing * * */
if(HighlightingUtils.isHighlightingEnabled(req) parsedUserQuery !=
null) {
String[] highFields = queryFields.keySet().toArray(new String[0]);
NamedList
Hi,
The Solr Highlighting docs says the following when it comes to picking
the default fields:
A comma- or space- delimited list of fields to generate highlighted
snippets for. If left blank, the fields highlighted for the
StandardRequestHandler are the defaultSearchField (or the df param
: which is the behavior that I expected, irrespective of whether the field has
: one or more values.
:
: Any idea what could be going on here?
not really ... but like i said, i'm not really a highlighter guy. I
can't think of any reason why having multiple values would cause this
behavior
On Wednesday 27 February 2008 03:58:14 Chris Hostetter wrote:
I'm not much of a highligher expert, but this *seems* like it was probably
intentional ... you are tlaking abouthte use case where you have a stored
field, and no term positions correct? ... so in order to highlight, the
highlighter
: I have created a Index of some xml files (xml's was created from mysql
: database) with solr. In xml's I have one text field. (more than 1000
: characters). Its searches fine, but solr result page is too long. I have
: tried highlight (hl=onhl.fl=fname), its shows highlighting results at end
Hello,
I have created a Index of some xml files (xml's was created from mysql
database) with solr. In xml's I have one text field. (more than 1000
characters). Its searches fine, but solr result page is too long. I have
tried highlight (hl=onhl.fl=fname), its shows highlighting results at end
after the fact)
: I would also like to have highlighting/snippets over all fields without
: appending all of them with hl.fl= . Something like hl.fl=* (would this be a
: big performance issue?)
it's not neccessarily a performance issue .. it's just not soemthing that
was ever really considered
Hi all,
I have a query like this:
q=(auto) AND id:(100 OR 1 OR 2 OR 3 OR 5 OR
6)fl=scorehl.fl=contenthl=truehl.fragsize=200hl.snippets=2hl.simple.pre=%3Cb%3Ehl.simple.post=%3C%2Fb%3Estart=0rows=10
Default field is content.
So, I expect, that only occurrencies of auto will be marked.
BUT:
Thank you! It works correct with filter query
Charlie Jackson schrieb:
I believe changing the AND id: etc etc part of the query to it's on
filter query will take care of your highlighting problem.
In other words, try a query like this:
q=(auto)fq=id:(100 OR 1 OR 2 OR 3 OR 5 OR
6)fl
seperater for highlighting multi-value fields
: The default field separator seems to be a '.' when highlighting
: multi-value fields. Can this be overridden in 1.2 to another
character?
Default field seperator where? in the response? can you give a
specific
example of what you are talking about
-Original Message-
From: Binkley, Peter [mailto:[EMAIL PROTECTED]
Sent: Wed 12/5/2007 4:07 PM
To: solr-user@lucene.apache.org
Subject: RE: Solr Highlighting, word index
We're doing a similar process using term vectors to look up the
bounding-box data in a custom response writer
: The default field separator seems to be a '.' when highlighting
: multi-value fields. Can this be overridden in 1.2 to another character?
Default field seperator where? in the response? can you give a specific
example of what you are talking about?
-Hoss
On 3-Dec-07, at 10:58 AM, Owens, Martin wrote:
You can tell lucene to store token offsets using TermVectors
(configurable via schema.xml). Then you can customize the request
handler to return the token offsets (and/or positions) by retrieving
the TVs.
I think that is the best plan of
On 5-Dec-07, at 1:02 PM, Owens, Martin wrote:
Thanks Mike, So in essence I need to write a new RequestHandler
plugin which takes the query string, tokenises it then perform a
some kind of action against the index to return results which I
should then be able to get the termVectors from?
looking at using
Lucene's new payload functionality.
Peter
-Original Message-
From: Mike Klaas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 05, 2007 2:19 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Highlighting, word index
On 5-Dec-07, at 1:02 PM, Owens, Martin wrote:
Thanks
1101 - 1200 of 1278 matches
Mail list logo