projects
/
idzebra-moved-to-github.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
8c2a7ff
)
added warning on clash betwen @attr 2=102 and @attr 9= some number
author
Marc Cromme
<marc@indexdata.dk>
Mon, 1 May 2006 13:07:40 +0000
(13:07 +0000)
committer
Marc Cromme
<marc@indexdata.dk>
Mon, 1 May 2006 13:07:40 +0000
(13:07 +0000)
doc/administration.xml
patch
|
blob
|
history
diff --git
a/doc/administration.xml
b/doc/administration.xml
index
4619e67
..
773edfd
100644
(file)
--- a/
doc/administration.xml
+++ b/
doc/administration.xml
@@
-1,5
+1,5
@@
<chapter id="administration">
<chapter id="administration">
- <!-- $Id: administration.xml,v 1.30 2006-05-01 12:59:33 marc Exp $ -->
+ <!-- $Id: administration.xml,v 1.31 2006-05-01 13:07:40 marc Exp $ -->
<title>Administrating Zebra</title>
<!-- ### It's a bit daft that this chapter (which describes half of
the configuration-file formats) is separated from
<title>Administrating Zebra</title>
<!-- ### It's a bit daft that this chapter (which describes half of
the configuration-file formats) is separated from
@@
-942,7
+942,7
@@
<para>
There are cases, however, where relevance of hit set documents is
<para>
There are cases, however, where relevance of hit set documents is
- hghly dependent on the query processed.
+ highly dependent on the query processed.
Simply put, <literal>dynamic relevance ranking</literal>
sortes a set of retrieved
records such
Simply put, <literal>dynamic relevance ranking</literal>
sortes a set of retrieved
records such
@@
-1074,6
+1074,17
@@
TF-IDF (Term Frequecy over Inverse Document Frequency) like algorithm.
</para>
TF-IDF (Term Frequecy over Inverse Document Frequency) like algorithm.
</para>
+ <warning>
+ <para>
+ Notice that <literal>dynamic ranking</literal> is not compatible
+ with <literal>estimated hit sizes</literal>, as all documents in
+ a hit set must be acessed to compute the correct placing in a
+ ranking sorted list. Therefore the use attribute setting
+ <literal>@attr 2=102</literal> clashes with
+ <literal>@attr 9=</literal>.
+ </para>
+ </warning>
+
<para>
It is possible to apply dynamic ranking on parts of the PQF query
allone:
<para>
It is possible to apply dynamic ranking on parts of the PQF query
allone: