I think it can be a subtask of LUCENE-3079 and we should first focus on the
general faceting features. As far as I know there is no bitset impl. out
there for faceting.
Op 14 jun. 2011 00:08 schreef "Jason Rutherglen" <[email protected]>
het volgende:
> Martijn, If the title is correct "Post grouping faceting" then maybe
> the bit set based system should be a separate issue? Eg, is there a
> bit set implementation today in LUCENE-3079?
>
> On Mon, Jun 13, 2011 at 2:58 PM, Martijn v Groningen
> <[email protected]> wrote:
>> There is already an issue open for this:
>> LUCENE-3079
>>
>> As the issues describes, the faceting in Solr relies on the schema (and
off
>> course the UIF).
>> So having the noting of a FieldType in the facet module would be very
>> helpful for selecting the right facet implementation.
>> Currently in Solr there is only one facet method for field facet that
work
>> per-segment,
>> but I think in the end we would want all facet types and methods to work
on
>> a per-segment basis.
>> Martijn
>> On 13 June 2011 23:47, Jason Rutherglen <[email protected]>
wrote:
>>>
>>> I think it's a better approach than rewriting Solr's internals. Eg,
>>> small development steps could be taken, using the knowledge learned
>>> from Solr's facet system. Eg, caching and intersecting bit sets would
>>> be an easy-ish first step?
>>>
>>> On Mon, Jun 13, 2011 at 2:37 PM, Simon Willnauer
>>> <[email protected]> wrote:
>>> > I believe people are already looking into that but I am not sure.
>>> > sounds reasonable to me but I think its going to be lots of work
>>> >
>>> > simon
>>> >
>>> > On Mon, Jun 13, 2011 at 11:34 PM, Jason Rutherglen
>>> > <[email protected]> wrote:
>>> >> Are we going the direction of creating full facet features outside of
>>> >> Solr? Eg, we have UIF extrapolated out, we can probably make a
module
>>> >> for bit set intersections as well. In the process the faceting will
>>> >> go per-segment.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: [email protected]
>>> >> For additional commands, e-mail: [email protected]
>>> >>
>>> >>
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: [email protected]
>>> > For additional commands, e-mail: [email protected]
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
