Re: query handling / multiple languages / multiple cores

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: query handling / multiple languages / multiple cores

Daniel Naber-10
On Thursday 18 October 2007 14:16, Henrib wrote:

> 1/ Anyone with the same kind of functional requirements? Is using
> multiple cores a bad idea for this need ?

Are documents sorted by relevance? Then this approach is problematic as you
cannot compare the result's score across different queries.

Regards
 Daniel

--
http://www.danielnaber.de
Reply | Threaded
Open this post in threaded view
|

Re: query handling / multiple languages / multiple cores

Henrib-2

I agree, the 2 document sets are not (should not be) mixed together; you get a list of FR docs and a list of EN docs (each list can be sorted by relevance).
However, not being able to compare result's score across different queries is something a lot of people can not (or dont want to) understand or hear. Some will even argue that this *is* the same query, that the index data obviously takes the language factor into account and normalizing by the highest score of the 2 lists is "ok"... And they'll add "the formula might be a little off but end-users like the result"...
Cheers

Daniel Naber-10 wrote
On Thursday 18 October 2007 14:16, Henrib wrote:

> 1/ Anyone with the same kind of functional requirements? Is using
> multiple cores a bad idea for this need ?

Are documents sorted by relevance? Then this approach is problematic as you
cannot compare the result's score across different queries.

Regards
 Daniel

--
http://www.danielnaber.de