: Well, it turns out the theoretical maximum for the Swing case is not
: Integer.MAX_VALUE, but is actually somewhere around 200 million due to
...
: In reality memory runs out sooner, which is why I was considering on-disk
: storage of the topdocs.
:
: But even if the user doesn't want to *see* the items which come back, quite
: often they do want to Select All and perform some operation (e.g. tag them,
I'm not sure where "Swing" came up in this thread ... or on-disk storage
(was that something you mentioned in another similar thread?)
But it don'treally see how it chagnes anything ... if your goal is to
perform an operating on every result in a set, why are you using
TopDocSCollector? why not write a HitCollector and perform your
operation in the collect method?
: copy the data to somewhere.) So regardless of the page size or the amount of
: data visible at any point in time, there is always the need to get the "set of
: every match" for any given search eventually.
I don't disagree with you, but is there a reason to have the entire set in
memory all at once regardless of it's size?
At the end of the day: people switching to using TopDocsCollector
instead of Hits are no worse off when trying to iterate over every result
in a ginormous result set, they're just have to define "ginormous"
for themselves, and the get an OOM right away instead of once they iterate
up to that many.
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
