search for: get_matches_estim

Hello, As I know, get_matches_estimated() return an estimate for the number of documents with matches the query. But now, I found it get a disparity between the return value and real mathced number. For an example: the real matched number is 58, but the return value is 458; so when the users click the hinder page, get a blank page ....

...; in different value ranges. I proceed building the query: Xapian::Query((foo:(pos=1) AND VALUE_RANGE 0 1286264160 1286264249)) and Xapian::Query((foo:(pos=1) AND VALUE_RANGE 0 1286264250 1286264339)) and so on... If I try to evaluate a quick estimate with: matches = enquire.get_mset(0, 0) matches.get_matches_estimated(); is it normal that the value range in my query is not evaluated? For each range i try, the estimated value is always the same, giving me a flat report. -- --------------------- Luca Barbieri

Hi, I'm getting quite odd results using get_matches_estimated() that I haven't seen before; we've just added a bunch of new data to the database. Xapian 1.0.7, checkatleast is set to 100. The database will get new stuff added to it automatically around 8.30am BST, so it's possible this might affect the links I provide, I guess. But I'...

Hi all, I found that the figure returned by MSet::get_matches_estimated() varies depending on how results are to be sorted. For instance, in my index, value 4 contains date and time in the format "yyyymmddhhmmss". For the same query, the number of results will be estimated to 20000+ when results are first sorted by date and time with set_sort_by_value_th...

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

Hi, is there a way to get the number of all possible matches for a specific query? Some api call like Xapian::doccount Xapian::Enquire::get_number_of_matches(); Best wishes Wilm

I've uploaded Xapian 1.0.20 (including Search::Xapian 1.0.20.0), which as usual you can download from: http://xapian.org/download The most notable changes in this release are: Xapian::MSet: * Fix incorrect values reported by get_matches_estimated(), get_matches_lower_bound(), and get_matches_upper_bound() in certain cases when sorting and collapsing (ticket#464). getopt-related build failures: * Fix build failure in xapian-core and omega on Mac OS X and possibly some other platforms (regression caused by fix for getopt-related...

In the Ruby bindings, set_X and get_X are renamed to remove the get/set, so MSet::get_matches_estimated() becomes a read-only property (if I have my terminology right) of the Ruby MSet class called matches_estimated. This matches how a Ruby programmer would expect a class to be designed. I was looking through the getters and setters list. I wonder if a few entries shouldn't be there, (the c...

...ellings_begin(); while( ! $i->equals( $database->spellings_end())) { var_dump( $i ); } echo '<hr />'; // Display the results. print $matches->get_matches_estimated() .' results found:<br />'."\n"; $i = $matches->begin(); while ( ! $i->equals($matches->end())) { $n = $i->get_rank() + 1; $data = $i->get_document()->g...

...1:OP_OR default query = qp.parse_query(terms) enquire = xapian.Enquire(database) enquire.set_weighting_scheme(xapian.BoolWeight()) enquire.set_query(query) enquire.set_docid_order(enquire.DESCENDING) matches = enquire.get_mset(0,10) print "%i results found . " % matches.get_matches_estimated() print "Results 1-%i:" % matches.size() for m in matches: print "rand= %-4d docid=%-8i" % (m.rank+1,m.docid), print " value:", xapian.sortable_unserialise(m.document.get_value(0)) except Exception, e: print "Exception : %s " % str(e)...

...->set_stemming_strategy(STEM_SOME); # $qp->set_default_op($defaultop); my $par = $qp->parse_query($query); my $enq = $db->enquire( $par ); my @matches = $enq->matches($nstart,$nrecords); my $mset = $enq->get_mset($nstart,$nrecords); my $est = $mset->get_matches_estimated(); my $totTime=0; foreach my $match ( @matches ) { my $doc = $match->get_document(); my $id = $match->get_docid(); my $eterm = $enq->get_matching_terms_end($id); my $bterm = $enq->get_matching_terms_begin($id); my @terms;...

...re($db); // Query for "php" or "mysql" $enq->set_query(new XapianQuery(XapianQuery::OP_OR, "php", "mysql")); // lets grab the matches! $mset = $enq->get_mset(0, 10); // output how many estimated echo 'Matches: '.$mset->get_matches_estimated().'<br/>'; // Output the terms that matched $terms = join(' ', $enq->get_matching_terms($mset->get_hit(0))); echo 'TERMS: '.$terms.'<br/>'; // Loop the matches and output some data.. for ($i = $mset->begin(); !$i->equ...

...oth cases the value of $msizeexact is "true". When I set HITSPERPAGE to 1000, the value of $msize is 418. So, it would seem that $msize does not take into account the collapsing of documents. However, I did some digging in the Omega code, and it seems $msize is the value of Xapian::MSet::get_matches_estimated(), and according to the API documentation, "This figure takes into account collapsing of duplicates, and weighting cutoff values.". I also have a smaller index (83937 documents) which uses the same script and the same kind of data, and there $msize is always correct. So, what causes...

...ME); Xapian::Query query = qp.parse_query(query_string); std::cout << "Parsed query is: " << query.get_description() << std::endl; enquire.set_query(query); Xapian::MSet matches = enquire.get_mset(0, 10); std::cout << matches.get_matches_estimated() << " results found.\n"; std::cout << "Matches 1-" << matches.size() << ":\n" << std::endl; for (Xapian::MSetIterator i = matches.begin(); i != matches.end(); ++i) { std::cout << i.get_rank() + 1 <...

...ME); Xapian::Query query = qp.parse_query(query_string); std::cout << "Parsed query is: " << query.get_description() << std::endl; enquire.set_query(query); Xapian::MSet matches = enquire.get_mset(0, 10); std::cout << matches.get_matches_estimated() << " results found.\n"; std::cout << "Matches 1-" << matches.size() << ":\n" << std::endl; for (Xapian::MSetIterator i = matches.begin(); i != matches.end(); ++i) { std::cout << i.get_rank() + 1 <...

...d::cout << "\nParsed query is: " << query.get_description() << "\n\n\n"; // Find the top 10 results for the query. enquire.set_query(query); Xapian::MSet matches = enquire.get_mset(0, 10); // Display the results. std::cout << matches.get_matches_estimated() << " results found.\n"; Xapian::Snipper snippet_generator; snippet_generator.set_stemmer(stemmer); snippet_generator.set_mset(matches); std::string snippet=snippet_generator.generate_snippet(text_to_index.text_str); std::cout << "\...

...dl ; Xapian::Query query = parser.parse_query(word); enquire.set_query(query); Xapian::MSet hits = enquire.get_mset(0, 10); //cout << "Parsed query is: " << query.get_description() << endl; // Display the results. cout << hits.get_matches_estimated() << " results found.\n"; cout << "Matches 1-" << hits.size() << ":\n" << endl; } end = high_resolution_clock::now(); auto diff = duration_cast<milliseconds>(end - start).count(); cout << "Average...

...new XapianQuery("visual");$oenquire = new XapianEnquire($odb);$oenquire->set_query($oquery);echo "<pre>"; echo "Perform: " . $oquery->get_description() . "<br/>";$omset = $oenquire->get_mset(0, 10); echo "Matches: " . $omset->get_matches_estimated() . "<br/>"; $oiter = new XapianMSetIterator();$oiter = $omset->begin(); while (!$oiter->equals($omset->end())){ $odoc = $oiter->get_document(); //Loop through values. echo "Rank: " . $oiter->get_rank() . "<br/>"; echo "%: "...

On 08/25/2013 05:02 PM, Olly Betts wrote: > So the simple fix is > probably just to install the perl-Search-Xapian RPM instead. Thanks, the Centos 6 repos don't have that rpm and the http://xapian.org/download page seems to only cover the XS bindings, if I am reading this correctly: But I was able to remove the rpm packages and compile and install the core and swig from source.

...<< "hello" << endl; + cout << *tmiter << endl; + } + + Xapian::Trie trie; // Parse the query string to produce a Xapian::Query object. Xapian::QueryParser qp; Xapian::Stem stemmer("english"); @@ -88,19 +107,19 @@ cout << matches.get_matches_estimated() << " results found:" << endl; for (Xapian::MSetIterator i = matches.begin(); i != matches.end(); ++i) { - cout << i.get_rank() + 1 << ": " << i.get_percent() << "% docid=" << *i - << " [" <&...