Ahhh, ignore my blather, I need more coffee. Somehow I was thinking
about something else.
Best
Erick
On Fri, Dec 17, 2010 at 8:16 AM, Erick Erickson wrote:
> Let's back up a bit here. What is the field definition for the field you're
> doing the range query on? i.e. [1 TO *]? And what are you tr
Let's back up a bit here. What is the field definition for the field you're
doing the range query on? i.e. [1 TO *]? And what are you trying
to accomplish with that clause (that is, all non-zero documents?
all documents? Do you have counts < 1?).
What version of Solr are you using?
You'll also ga
Now I think that hl.requireFieldMatch=false is a problem, because
there is no meaning to match query string of "kcmeta/view/count" to
the high-light field "title" and "body". To support for full-text
query field search matching high-light fields, I think it's better to
add same query condition on "
> > Adding &hl.requireFieldMatch=true should probably
> solve your problem.
> >
> Yes, adding &hl.requireFieldMatch=true can solve my
> problem, but in my
> solution , I have a "content" field indexing all fields'
> contents to
> support full text search, but I also have another 2 fields
> "title"
Thank you for reply.
> Are you using hl.highlightMultiTerm=true? Pasting your search URL can give
> more hints.
>
Yes, I used the "hl.highlightMultiTerm=true" , my search query is as follows :
start=0&rows=10&facet.mincount=1&facet.field=authornav&facet.field=contentsearchkeywordnav&facet.field=
> I got an error as follows when I do a range query search
> ([1 TO *])
> on an numeric field and highlight is set on another text
> field.
Are you using hl.highlightMultiTerm=true? Pasting your search URL can give more
hints.
Adding &hl.requireFieldMatch=true should probably solve your problem.
