Re: prioritizing aggregated DBs
Eric Wong <[email protected]> Fri, 21 Feb 2020 19:20:22 +0000
| Newsgroups | gmane.comp.search.xapian.general |
|---|---|
| Message-ID | <20200221192022.GA28370@dcvr> |
Olly Betts <[email protected]> wrote: > On Wed, Feb 19, 2020 at 10:23:09AM +0000, Eric Wong wrote: > > Btw, is there a way to quickly figure out which sub-DB a retrieved > > document or mset item belongs to? > > Yes: https://trac.xapian.org/wiki/FAQ/MultiDatabaseDocumentID > > 1.4.12 added a Database::size() method which reports the number of > shards - for older versions you have to keep track of that yourself > (which needs a little care as add_database() "flattens", so after > db1.add_database(db2) db1.size() will have increased by db2.size() > (which could be 0 if db2 has no shards). Thanks, I'll have to use the older ways... Btw, is the XS Perl binding going to be updated for Database::size()? Or is the SWIG binding the only way forward? Fwiw, I also wrote about some issues I found with the SWIG binding sometime back: https://trac.xapian.org/ticket/523#comment:13 (but I've worked around the issues and public-inbox supports both SWIG and XS on FreeBSD systems) I'm mainly on Debian 10, and there'll still be users on CentOS 7.x for a while :<