From: Marc Cromme Date: Mon, 3 Jul 2006 11:30:59 +0000 (+0000) Subject: small updates X-Git-Tag: ZEBRA.2.0.0~50 X-Git-Url: http://git.indexdata.com/?p=idzebra-moved-to-github.git;a=commitdiff_plain;h=41107f15886b1645510c9dd82e067d56a6751b10 small updates --- diff --git a/doc/querymodel.xml b/doc/querymodel.xml index ff0107b..cdf0d72 100644 --- a/doc/querymodel.xml +++ b/doc/querymodel.xml @@ -1,5 +1,5 @@ - + Query Model @@ -227,7 +227,7 @@ idxpath Hardwired XPATH like attribute set, only available for indexing with the GRS record model - depreciated + deprecated --> @@ -607,7 +607,8 @@ Escaping PQF keywords and other non-parseable XPath constructs - with '{ }' to prevent syntax errors: + with '{ }' to prevent client-side PQF parsing + syntax errors: Z> find @attr {1=/root/first[@attr='danish']} content Z> find @attr {1=/record/@set} oai @@ -994,7 +995,7 @@ Any position in field 3 - default + supported @@ -1002,9 +1003,9 @@ The position attribute values first in field (1), and first in subfield(2) are unsupported. - Using them does not trigger an error, but silently defaults to - any position in field (3). - + Using them silently maps to + any position in field (3). A proper diagnostic + should have been issued. @@ -1349,7 +1350,7 @@ Complete subfield 2 - depreciated + deprecated Complete field @@ -1535,6 +1536,19 @@ + + + + + Zebra Extension Rank Weight Attribute (type 9) @@ -1578,17 +1594,23 @@ Zebra Extension Approximative Limit Attribute (type 9) - Newer Zebra versions normally estimate hit count for every APT + Zebra computes - unless otherwise configured - + the exact hit count for every APT (leaf) in the query tree. These hit counts are returned as part of the searchResult-1 facility in the binary encoded Z39.50 search response packages. - By setting a limit for the APT we can make Zebra turn into - approximate hit count when a certain hit count limit is - reached. A value of zero means exact hit count. + By setting an estimation limit size of the resultset of the APT + leaves, Zebra stoppes processing the result set when the limit + length is reached. + Hit counts under this limit are still precise, but hit counts over it + are estimated using the statistics gathered from the chopped + result set. + Specifying a limit of 0 resuts in exact hit counts. + For example, we might be interested in exact hit count for a, but for b we allow hit count estimates for 1000 and higher. @@ -1598,8 +1620,16 @@ The estimated hit count facility makes searches faster, as one only needs to process large hit lists partially. + It is mostly used in huge databases, where you you want trade + exactness of hit counts against speed of execution. + Do not use approximative hit count limits + in conjunction with relevance ranking, as re-sorting of the + result set obviosly only works when the entire result set has + been processed. + + This facility clashes with rank weight, because there all documents in the hit lists need to be examined for scoring and re-sorting. @@ -1745,7 +1775,7 @@ main Zebra configuration file zebra.cfg directive attset: idxpath.att must be enabled. - The idxpath is depreciated, may not be + The idxpath is deprecated, may not be supported in future Zebra versions, and should definitely not be used in production code. @@ -1778,31 +1808,31 @@ XPATH Begin 1 _XPATH_BEGIN - depreciated + deprecated XPATH End 2 _XPATH_END - depreciated + deprecated XPATH CData 1016 _XPATH_CDATA - depreciated + deprecated XPATH Attribute Name 3 _XPATH_ATTR_NAME - depreciated + deprecated XPATH Attribute CData 1015 _XPATH_ATTR_CDATA - depreciated + deprecated