search for: op_value_rang

...ch does with terms: std::set<std::string> terms; // notmuch populates terms via terms.insert(*i)... Query(OP_OR, terms.begin(), terms.end()); // Disclaimer: I don't really know C++ With a set of integers I have (after sortable_serialise), would the best way be to OP_OR a bunch of OP_VALUE_RANGE queries together? So, perhaps something like: Query(OP_OR, Query(OP_VALUE_RANGE, column, v[0], v[0]), Query(OP_VALUE_RANGE, column, v[1], v[2]), Query(OP_VALUE_RANGE, column, v[3], v[3]), ... Query(OP_VALUE_RANGE, column, v[LAST], v[LAST])) // Or (totally not even compile-tested and...

...y, filter); The notmuch way will match nothing for that case so you need to conditionalise applying the filter (assuming you still want to match something when there are no filter terms). > With a set of integers I have (after sortable_serialise), would the > best way be to OP_OR a bunch of OP_VALUE_RANGE queries together? > > So, perhaps something like: > > Query(OP_OR, > Query(OP_VALUE_RANGE, column, v[0], v[0]), > Query(OP_VALUE_RANGE, column, v[1], v[2]), Did you mean 1 and 1 here? > Query(OP_VALUE_RANGE, column, v[3], v[3]), > ... > Query(OP_VALUE_RANG...

...which satisties specific condition, such as contain the term of "shirt" and "white", and "price <= 500" and "comment count >= 100", "1000 <= click_number <= 2000". And we have two methods: 1, use xapian.Query for terms and xapian.Query.OP_VALUE_RANGE to filter the value. 2, use xapian.Query for terms to get candidates, then use xapian.MatchDecider to filter the value. Which method get a better performance?

HI, all, I am a user of Xapian, and now I have a problem in using it. After using boolean terms to get some candidates of documents (still too much), we want sorted them by self-defined function which is used in Xapian::KeyMaker->operator(). But how can I get the serialise score in Xapian::MSetIterator object. c++ code likes this: class SortKeyMaker : public Xapian::KeyMaker { std::string

...ing the match in some cases. Fixes ticket#476. * OP_XOR with non-leaf subqueries could skip matching documents in some cases, and OP_XOR of three or more sub-queries could return incorrect weights. Fixes ticket#475. * OP_OR is now more efficient if a subquery is potentially expensive (e.g. OP_VALUE_RANGE, OP_NEAR, OP_PHRASE, PostingSource). A 10-fold speed-up with OP_VALUE_RANGE has been observed. Build System: * Install files to make Xapian easier to use with cmake. Portability * On x86 processors, Xapian now defaults to using SSE2 FP instructions. This avoids issues with excess precisi...

...ork done that yield inconsistent results. What I am trying to point out is that we need start to think about using natural language processing when placing infrastructure for Xapian. So far we have the following OP_AND, OP_AND_MAYBE, OP_AND_NOT, OP_ELITE_SET, OP_FILTER, OP_NEAR, OP_OR, OP_PHRASE, OP_VALUE_RANGE, OP_XOR search operators and we could add one more OP_NLP. What we can do now is to implement OP_NLP to tagged nouns, adjectives, adverbs, punctuations, foreign words etc. Calculate relation between them and assign boost value to the most occurred terms in query for example noun. Search query e...

Hi, I want to update a document. The document is identified by the document path e.g. /home/user/file.txt. To find the doc id by the path I need to assign the path to the document. In the FAQ is supposed to add the doc id (the path) as a term to the document. My idea is to at the path as a value by #define PATH_ID 0 add_value(PATH_ID, "/home/user/file.txt") and then do a query: