search for: termpos

...on of terms is saved with gap. This is not happening with scriptindex.cc While this is happening ? Another question is why in omindex.cc the term possition starts with 0 while in scriptindex it starts from 1 ? Code snippet from omindex.cc // Add postings for terms to the document Xapian::termpos pos = 1; pos = index_text(title, newdocument, stemmer, pos); pos = index_text(dump, newdocument, stemmer, pos + 100); pos = index_text(keywords, newdocument, stemmer, pos + 100); Code snippet from scriptindex.cc Xapian::termpos wordcount = 0; ........... for (i = v.begin(); i != v.end...

...oid add_value (Xapian::valueno valueno, const std::string &value) What's the purpose of this method? Document will related to the terms, but what's the purpose of this? (2) add_posting method will add term to a documents. void add_posting (const std::string &tname, Xapian::termpos tpos, Xapian::termcount wdfinc=1) I noticed that Xapian::TermGenerator has follow method void index_text (const Xapian::Utf8Iterator &itor, Xapian::termcount weight=1, const std::string &prefix="") What's the differences and relationship between these two functions?...

...he classical constructor Xapian::Query<http://xapian.org/docs/apidoc/html/classXapian_1_1Query.html#f396e213df0d8bcffa473a75ebf228d6>(const std::string &tname_, Xapian::termcount<http://xapian.org/docs/apidoc/html/namespaceXapian.html#72b5a76dd8cfb7b251fe7986e86390cb>wqf_=1, Xapian::termpos<http://xapian.org/docs/apidoc/html/namespaceXapian.html#e5a16f073d0c8ed54085a9de07248d45>pos_=0) : Xapian::Query query_test(Xapian::Query::OP_OR, Xapian::Query("Bonjour", 10), Xapian::Query("Hello", 5)); Xapian::TermIterator qt = query_test.get_terms_begin();...

...al constructor Xapian::Query<http://xapian.org/docs/apidoc/html/classXapian_1_1Query.html#f396e213df0d8bcffa473a75ebf228d6>(const std::string &tname_, > Xapian::termcount<http://xapian.org/docs/apidoc/html/namespaceXapian.html#72b5a76dd8cfb7b251fe7986e86390cb>wqf_=1, > Xapian::termpos<http://xapian.org/docs/apidoc/html/namespaceXapian.html#e5a16f073d0c8ed54085a9de07248d45>pos_=0) : > > Xapian::Query query_test(Xapian::Query::OP_OR, Xapian::Query("Bonjour", > 10), Xapian::Query("Hello", 5)); > Xapian::TermIterator qt = query_test.get_...

...hanged behind the scenes. I can see two fixes for this: (a) implement a "deep copy" clone for Query objects and use it in Enquire::set_query() (b) make Query object immutable by replacing these non-const public methods with extra constructor parameters: void set_window(Xapian::termpos window); void set_cutoff(Xapian::weight cutoff); void set_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...

Hi, Sorry to follow up on an old thread, but I am wondering if there has been any work done on, or interest in, increasing the maximum document id beyond a 32bit limit? Daniel On Mon, Jun 18, 2007 at 04:11:54AM +0100, Olly Betts wrote: > > In particular, there is currently a limit of 4 billion documents in a > > database, due to using a 32 bit type for document IDs, but I don't

...s & QueryParser::FLAG_AUTO_MULTIWORD_SYNONYMS) { + #endif // Check for multi-word synonyms. Database db = state->get_database(); *************** *** 1432,1440 **** --- 1449,1467 ---- // Use the position of the first term for the synonyms. Xapian::termpos pos = (*begin)->pos; + #ifdef HAVE_SYNONYMS_ENH + string prefix; + const list<string> & prefixes = (*begin)->prefix_info->prefixes; + if (prefixes.begin() != prefixes.end()) + prefix = *(prefixes.begin()); + #endif begin = i...

>A possible workaround (and perhaps a better approach) would be to >set BoolWeight as the weighting scheme, then feed in your score as >a weight using a PostingSource. Then it's available via get_weight() >on the MSetIterator object: > >https://getting-started-with-xapian.readthedocs.io/en/latest/advanced/postingsource.html > >You may find that's faster because