X-Git-Url: http://git.indexdata.com/?p=idzebra-moved-to-github.git;a=blobdiff_plain;f=NEWS;h=6248ac8d4c3ec3a3d3ce43cde477bb9224a47568;hp=9f8543516fbcbe5730a159177ff87d44aff63126;hb=4097bac1dce126e79ce1550fad8b2034a311ff80;hpb=4e67b823f05b521f193af096a40c0f64758c5fc1 diff --git a/NEWS b/NEWS index 9f85435..6248ac8 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,50 @@ +Added zebraidx command, adelete, which attempts to delete records. +It's like 'delete', but does not fail if a record does not exist. + +--- 2.0.20 2007/12/19 + +Added experimental support for faceted results. This is implemented +as a special retrieval on a result set and is triggered using element +set name zebra::facet::f1:t1,f2,t2,.. which will return terms and +hit counts for field f1, type t1, field f2, type t2, .. The returned +data is packed as XML or SUTRS depending on record syntax. + +Added support for Unicode-based indexing using ICU. This allows +locale specific scanning, sorting. The implementation is based on +the ICU utility part of YAZ 3.0.16 and later. See the manual as well +as the examples/marcxml for an example of the use of ICU. + +--- 2.0.18 2007/09/19 + +Fixed bug with scan and staticrank enabled. Bug introduced in 2.0.16. + +--- 2.0.16 2007/09/12 + +Scan now returns a displayTerm which closer to the original word/phrase +from original record. + +Added snippet support. Element set name zebra::snippet will make +Zebra return an XML record with snippets (terms around matching terms). + +Fixed bug #1142: Non-indexed but listed attributes issues diagnostic. + +Fixed bug #1131: Missing value-of data in DOM filter. + +Fixed bug #1049: zebra.cfg lines with leading space are ignored. + +Fixed bug #1128: sortmax not honored. + +Fixed bug #1121: Crash for some searches with customized string.chr. + +--- 2.0.14 2007/05/09 + +Zebra uses the YAZ 3 API. Note that this changes the Zebra API +as well. The register layout is the same however. + +Fixed bug #1114: scan within set may use excessive CPU. + +Fixed memory leak that occurred in scan. + Fixed memory leak that occurred for each deleted record. Optimize updates of records where content is almost identical to previous