On Monday 12 April 2004 20:54, [EMAIL PROTECTED] wrote:
On Sunday 11 April 2004 17:46, Erik Hatcher wrote:
In other words, you need to invent your own pattern here?! :)
I just experimented a bit and came up with the ValueListSupplier which
replaces the ValueList in the VLH. Seems to work so
On Sunday 11 April 2004 17:46, Erik Hatcher wrote:
In other words, you need to invent your own pattern here?! :)
I just experimented a bit and came up with the ValueListSupplier which
replaces the ValueList in the VLH. Seems to work so far... :-) Comments are
greatly appreciated!
Timo
On Saturday 10 April 2004 20:40, Erik Hatcher wrote:
Thats the beauty it is up to you to load the doc iff you want it.
As I want all of them I don't see why this should be faster at all...
-
To unsubscribe, e-mail: [EMAIL
On Apr 11, 2004, at 5:25 AM, [EMAIL PROTECTED] wrote:
On Saturday 10 April 2004 20:40, Erik Hatcher wrote:
Thats the beauty it is up to you to load the doc iff you want it.
As I want all of them I don't see why this should be faster at all...
Then have a look at the Hits class. It is doing
On Sunday 11 April 2004 13:40, Erik Hatcher wrote:
using a HitCollector you are bypassing those mechanisms. Whether it is
measurably faster would depend on several other factors.
Well, it is hardly faster, so this is no real solution :-\
On Saturday 10 April 2004 20:40, Erik Hatcher wrote:
Thats the beauty it is up to you to load the doc iff you want it.
Well, there's another problem with HitCollector: the list I build is not
sorted by score :-(
-
To
On Apr 11, 2004, at 9:32 AM, [EMAIL PROTECTED] wrote:
On Saturday 10 April 2004 20:40, Erik Hatcher wrote:
Thats the beauty it is up to you to load the doc iff you want it.
Well, there's another problem with HitCollector: the list I build is
not
sorted by score :-(
HitCollector was just an
On Apr 11, 2004, at 10:00 AM, [EMAIL PROTECTED] wrote:
On Sunday 11 April 2004 15:56, Erik Hatcher wrote:
HitCollector was just an option - and apparently not the right one for
your use.
So, any other option? :-)
Well, yes the one we already discussed. Let your presentation tier
talk
On Sunday 11 April 2004 17:16, Erik Hatcher wrote:
Well, yes the one we already discussed. Let your presentation tier
talk directly to Hits, so you are as efficient as possible with access
to documents, and only fetch what you need.
Again, don't let patterns get in your way.
Well, the
On Apr 11, 2004, at 11:28 AM, [EMAIL PROTECTED] wrote:
On Sunday 11 April 2004 17:16, Erik Hatcher wrote:
Well, yes the one we already discussed. Let your presentation
tier
talk directly to Hits, so you are as efficient as possible with access
to documents, and only fetch what you need.
On Friday 09 April 2004 23:59, Ype Kingma wrote:
When you need 3000 hits and their stored fields, you might
consider using the lower level search API with your own HitCollector.
I apologize for the stupid question but ... where's the actualy result in
HitCollector? :-)
collect(int doc,
On Apr 10, 2004, at 5:08 AM, [EMAIL PROTECTED] wrote:
On Friday 09 April 2004 23:59, Ype Kingma wrote:
When you need 3000 hits and their stored fields, you might
consider using the lower level search API with your own HitCollector.
I apologize for the stupid question but ... where's the actualy
On Apr 9, 2004, at 3:18 PM, [EMAIL PROTECTED] wrote:
I implemented a VLH pattern Lucene's search hits but noticed that
hits.doc()
is quite slow (3000+ hits took about 500ms).
So, I want to ask people here for a solution. I tought about something
like a
wrapper for the VO (value/transfer
Patterns are work-arounds for language deficiences :)
Don't use patterns because some book said so - use them if they are the
pragmatic choice. Flattening data for reports or search results and
perhaps being a little more coupled to Lucene between tiers in order to
avoid performance problems
On Friday 09 April 2004 21:18, [EMAIL PROTECTED] wrote:
Hi!
I implemented a VLH pattern Lucene's search hits but noticed that
hits.doc() is quite slow (3000+ hits took about 500ms).
So, I want to ask people here for a solution. I tought about something like
a wrapper for the VO
15 matches
Mail list logo
