[Xesam] Why is vendor.maxhits read-only?

Joe Shaw joe at joeshaw.org
Mon Dec 17 19:25:44 PST 2007


Hi,

On 12/17/07, Mikkel Kamstrup Erlandsen <mikkel.kamstrup at gmail.com> wrote:
> On 17/12/2007, Anders Rune Jensen <anders at iola.dk> wrote:
> > Ok, maybe I misunderstand this completely but it isn't always easy to
> > get all the details from source in a jif (even if it's Python :-)).
>
> No not necessarily. I think you are thinking about databases, in
> (most) database systems it is almost free to look up the values of the
> fields. This is not necessarily so in a Lucene index for instance.

Right.  Beagle, for instance, only returns a few hundred results,
although there might be tens of thousands of items which match the
search.  The reason for this is (a) users will never see even the few
hundred items and (b) it is complex computationally to construct all
those hits, sort them, etc.  For this, Beagle would probably set that
value to a few hundred.

You can configure Beagle to return more than a few hundred results
per-search, though.

Joe


More information about the Xesam mailing list