search for: collapse_key

On Thu, Dec 18, 2014 at 11:38:42PM +0000, James Aylett wrote: > Collapsing is done using a valueno (you can tell because collapse_key > is of type Xapian::valueno), which is a 32 bit unsigned integer (see > here: > https://getting-started-with-xapian.readthedocs.org/en/latest/concepts/indexing/values.html). > For 32 bit unsigned you need unsigned long. Xapian::valueno is actually a typedef for unsigned currently. Wh...

...1000) needs to track 3000 entries so this won't reduce your heap usage (at least not peak usage). Is the heap usage problematic? Looking at the code, for git master each entry is currently: double weight; Xapian::docid did; Xapian::doccount collapse_count; std::string collapse_key; std::string sort_key; We're always going to need the docid, but the other fields aren't always needed and this could be slimmed down depending on what options are in use if the size is causing problems. It is as it is just for simplicity really. If you're using libstdc+...

Hello, I came across the file *omega.cc* which is in directory* xapain-application/omega/* In this file , atoi is used in *Percentage Relevance cutoff *(293 line no) as Percentage lies between 0-100 their is no need to modify atoi . But do we need to check for error's ? Second Implementation is in *collapsing* (301) in which we collapse set of document under a key,range of this key has not

In other words, is it possible to avoid duplicates if new documents are inserted into the DB by another process in-between ->get_mset calls when reusing Xapian::Enquire objects? I do some expensive processing on each mset window, so I always limit the results to limit heap usage even if I'm planning on going through a big chunk of the DB: $mset = $enq->get_mset(0, 1000);