Chris Hostetter wrote:
: :
: : text^0.5 features^1.0 name^1.2 manu^1.1
: :
: > if the q param is: albino elephant ... what would it mean that text and
: > feature are mandatory? do both words have to appear in text and in
: > feature, or just one in each?
: What I wanted
: :
: : text^0.5 features^1.0 name^1.2 manu^1.1
: :
: > if the q param is: albino elephant ... what would it mean that text and
: > feature are mandatory? do both words have to appear in text and in
: > feature, or just one in each?
: What I wanted is that 'albino' 'eleph
Chris Hostetter wrote:
: Is it possible to specify precisely one or more mandatory fields in a
: DismaxRequestHandler?
what would the semantics making a field mandatory mean? considering your
specific example...
:
: text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
I think I have the same question as Arnaud. For example, my dismax query has
qf=title^5 description^2. Now if I search for "Java developer", I want to
make sure that the results have at least "java" or "developer" in the title.
Is this possible with dismax query?
On 7/30/07, Chris Hostetter <[EMAI
: Is it possible to specify precisely one or more mandatory fields in a
: DismaxRequestHandler?
what would the semantics making a field mandatory mean? considering your
specific example...
:
: text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
:
:
Hello,
Is it possible to specify precisely one or more mandatory fields in a
DismaxRequestHandler?
Something like that:
explicit
0.01
text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
text^0.2 features^1.1 name^1.5 manu^1.4 manu_exact^1
