: > Hmmm, i see ... well the easiest way to go is not to worry about it when
: > parsing the query, when you go to compute facets for all hte fields you
: > tink might be useful, you'll see that only one value for "brand" matches,
: > and you can just skip it.
: I would think that this is not the
On Thu, 2007-08-23 at 10:44 -0700, Chris Hostetter wrote:
> : Probably I'm also interested in PrefixQueries, as they also provide a
> : Term, e.g. parsing "ipod AND brand:apple" gives a PrefixQuery for
> : "brand:apple".
>
> uh? ... it shoudn't, not unless we're talking about some other
> customiz
: Probably I'm also interested in PrefixQueries, as they also provide a
: Term, e.g. parsing "ipod AND brand:apple" gives a PrefixQuery for
: "brand:apple".
uh? ... it shoudn't, not unless we're talking about some other
customization you've already made.
: I want to do s.th. like "dynamic facet
On Wed, 2007-08-22 at 23:18 -0700, Chris Hostetter wrote:
> : in my custom request handler, I want to determine which fields are
> : constrained by the user.
> :
> : E.g. the query (q) might be "ipod AND brand:apple" and there might
> : be a filter query (fq) like "color:white" (or more).
> :
> : W
: in my custom request handler, I want to determine which fields are
: constrained by the user.
:
: E.g. the query (q) might be "ipod AND brand:apple" and there might
: be a filter query (fq) like "color:white" (or more).
:
: What I want to know is that "brand" and "color" are constrained.
techni
Hello,
in my custom request handler, I want to determine which fields are
constrained by the user.
E.g. the query (q) might be "ipod AND brand:apple" and there might
be a filter query (fq) like "color:white" (or more).
What I want to know is that "brand" and "color" are constrained.
AFAICS I co
