Chris,
Thanks for your reply, I got what you said. In my case, I have the
following requirements:
1. search on different fields
2. highlight the query string in searching fields, not default search
field
3. Use wildcard
I think the only option I have is to use standard request handler and
specify
: 1. search on different fields
: 2. highlight the query string in searching fields, not default search
: I think the only option I have is to use standard request handler and
: specify which field I want to search and add the same field to hl.fl,
: something similar to ?q=TITLE:consult*&hl=on&hl
Hello All,
I've been working with solr on Tomcat 5.5/Windows and had success
setting my solr home using the context fragment. However, I cannot get
it to work on Tomcat 5.028/Unix. I've read and re-read the Apache
Tomcat documentation and cannot find a solution. Has anyone run into
this issu
Good point, I haven't thought about it. It makes sense to use
requireFieldMatch in my case.
One more question about using wildcard. I found if wildcard is used in
the query, the highlight elements only shows unique id, it won't display
the field information(See below, the arr section in blue is re
As far as I understand, I can put multiple doc types in the same
index, for example, web pages, images, products, etc. In order
to do so, I think I need to do the following:
- have a doctype field (not necessary but nice to have)
- add all possible fields of all doc types in schema
- when querying
: This is based on my understanding that solr/lucene does not
: have the concept of document type. It only sees fields.
:
: Is my understanding correct?
it is.
: It seems a bit unclean to mix fields of all document types
: in the same schema though. Or, is there a way to allow multiple
: documen
: One more question about using wildcard. I found if wildcard is used in
: the query, the highlight elements only shows unique id, it won't display
:
:
:
: Consultant
your description of the problem doesn't seem to match what you've pasted
... it looks like it's highlighting just the p
Yes, I'm using 1.1. The example in my last email is an expected result,
not the real result. Indeed I didn't see the arr element in the
highlighting element when either prefix wildcard or true wildcard query
is used.
I just tried nightly build, as you said, it works great except for
prefix wildcard
