On Jan 12, 2007, at 8:26 PM, Chris Hostetter wrote:
Yeah ... what Erik's talking about really sounds like a simple
faceting
issue: supporting prefix's for limiting the list of constraints ...
what
Tracey was talking about seems much more like Luke-esqe index info:
what
are all the fields, and what are all the terms in those fields.
(and what
is the docFreq of each of those terms)
The only difference in that last bit and the faceting in my stuff
returns all terms in a field only for the documents that match some
constraints (fq kinda stuff).
: > Paging via start/
: > rows is necessary,
:
: Hmmm, really? Not too hard I guess, but I'd be interested in how
you use it.
yeah paginating facet constraints doesn't really make sense to me ...
unless you're just taling about paginated the main results like we
already
do now. for the facets themselves facet.limit seems good enough ..
especially since it already sorts.
Suppose there are a 1000 terms that start with "foo"... the user
would like to see them all, but page through them rather than see
them all at once. facet.limit could be increased to get more back,
but I'd like to have the ability to get 50 at a time, in pages.
I get why pagination is important in Tracey's use case though (where
she's just dumping all terms)
My stuff dumps terms too, just not all of them, only ones that start
with a prefix, which could still be more than the client wants in one
shot. Sure, the client could buffering it, but it seems Solr would
be better adept at being efficient about it.
Erik
