search for: set_collapse_key

Greets, Is it possible to obtain the actual match count if you're using set_collapse_key()? ie, the total count *before* the collapsing occurs (without using get_mset()). Alternatively, will MSet::get_matches_estimated() return the true - pre-collapse - count, or will it also be affected by collapsing? Thanks Henry

...problem with collapsing by a key in a compound database. I have 2 databases (e.g. clients and client branches), both of them have the same attribute (with the same valueno), `client_id'. What I need is to search in both these databases and collapse results by `client_id' to get client IDs (set_collapse_key is used with collapse_max=1). The problem is that I receive 2 equal `client_id' values in the MSet (one per database?). Is it possible to get unique collapsed values when searching in a compound database?

Hello It is possible somehow to give higher priority to recent document. For example, when adding new document to the database, I will add a term that specifies date of the document. During the search, the date of the document is taken into account in the algorithm that calculates document relevancy. In another project I am working on, I would like to limit number of pages returned from the

Hi I know it might not possible, but just want to try my luck. say, for a web search engine backed by xapian.... Is it possible to group the result by domain just like google's [ More results from www.abc.com ], when there are more than 1 results from the same domain? Or, anyone have some work around to do it? Cheers Andrey Kong

Hi all, I am trying to implement an Incremental indexing scheme. The problem is that usually the modified documents are large but the modifications are limited. Ideally, I would like to reindex only the modified parts of these documents. If I am not mistaken, xapian cannot do that. Are there any other approaches? It would be nice if xapian supported something like the SQL "group by".

...y(OP_VALUE_RANGE, column, v, v)); } Query(OP_OR, subq.begin(), subq.end()); It seems what I'm really looking for is an OP_VALUE_OR or OP_VALUE_IN; but only OP_VALUE_{GE,LE,RANGE} exists. [1] Even if I switched to terms, I would still keep the numeric values since I also rely on Enquire.set_collapse_key on this column.