Well, I have problems using the "filter" terminology. People who have
traditionally known the "facet.prefix" parameter would like to stick to
that. Having both of these might lead to confusion.
I have no problems with using local param syntax though. This should be
fine:
facet.field={!prefix=foo prefix=bar}myfield
Filtering within facets is a good idea but lets limit the scope of this
enhancement to multiple "facet.prefix" values for any facet.field.
Cheers
Avlesh
On Fri, Aug 21, 2009 at 11:54 AM, Yonik Seeley
<yo...@lucidimagination.com>wrote:
> On Fri, Aug 21, 2009 at 2:18 AM, Avlesh Singh<avl...@gmail.com> wrote:
> > So, this is it -
> > facet.field=myField&f.foo.facet.prefix=foo&f.foo.facet.prefix=bar
> > Right?
>
> I'd actually prefer a more non-ambiguous and general syntax.
> It seems like you want to include a filter in faceting that you don't
> want applied to the normal search results (else you would have just
> used fq=myfield:(A* OR B*))
>
> So what about something like:
>
> facet.field={!filter="myfield:A* OR B*"}myfield
> or with dereferencing,
> facet.field={!filter=$f}myfield&f=myfield:A* OR B*
>
> -Yonik
> http://www.lucidimagination.com
>
