search for: op_elite_set

Hi, When we use OP_ELITE_SET we can specify the number of terms we want to use. In http://trac.xapian.org/wiki/FAQ/EliteSet there is this text: "The number of terms which OP_ELITE_SET will use defaults to 10 (or ceil(sqrt(number_of_subqueries)) if there are more than 100 subqueries), but may be set by specifying a parame...

...============================================================== --- include/xapian/query.h (revision 7553) +++ include/xapian/query.h (working copy) @@ -95,7 +95,15 @@ /** Select an elite set from the subqueries, and perform * a query with these combined as an OR query. */ - OP_ELITE_SET = 10 + OP_ELITE_SET = 10, + + /** Match no documents. + * + * This operator takes no subqueries, and matches no documents. + * It can be a useful placeholder when parsing query strings, if + * a portion of the query can be shown to m...

...ssing is not a new thing and there has been lot of work 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 occu...

...elite_set_size(Xapian::termcount size); Xapian::termcount set_length(Xapian::termcount qlen); The private non-const methods are only used during construction, so they're not a problem. I tend to favour (b). The first three are tied to particular OPs (OP_NEAR/OP_PHRASE, OP_WEIGHT_CUTOFF, and OP_ELITE_SET respectively) so are perhaps cleaner that way anyway. The last is more awkward as a constructor parameter - it would perhaps be better replaced by an optional parameter to Enquire::set_query(). This is an API change (unlike (a)), but not one which is hard to update user code for. I don't hav...

Hello, I have updated to Xapian 1.1.4 and maybe there is a memory leak. I can run only dmalloc - valgrind would be much too slow. How can I build a debug-build of xapian? Thanks a lot Marcus

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

Hi Everybody, Here is the first version of my match for an ExternalPostList, it should apply cleanly to 0.9.5 and 0.9.6. You can use it by first implementing an ExternalPostingSource, then creating a new Query object passing a reference an instance of your implementation to the constructor, see query.h. The ExternalPostingSource implementation is reference counted, so when its no