search for: positionlist

...machine learning" it mostly returns documents containing "machine learning" but it also returns documents containing only learning but not machine. I do not know if the two are related but it seems to have started happening at about the same time. The other problem is that I use the positionlist to generate a dynamic summary which obviously no longer works. I'm using version 1.2.0 with the ruby bindings and database type is chert. I just ran xapian-check on the index and it came back with: position: Lazily created, and not yet used. Which I guess answers my immediate question b...

The following piece of code triggers an 'unimplemented' exception with the message: "Can't use NEAR/PHRASE with a subexpression containing NEAR or PHRASE" Xapian::Query or1(Xapian::Query::OP_OR, Xapian::Query("one"), Xapian::Query("two")); Xapian::Query or2(Xapian::Query::OP_OR, Xapian::Query("three"),

...ake sense in this case, if there is a wishlist somewhere, but it's admittedly not an issue that most users will be concerned with...). > * Currently the OP_OR subqueries can only have two subqueries of their own. > Lifting this restriction needs a bit of work on the new > OrPositionList class > - the old patch used a series of pairwise OrPositionList objects, but the > new patch needs a single one instead - the class needs reworking to handle > that. > > So I think the second limitation needs addressing, and of course any bugs > resolving. I am...

Olly Betts writes: > On Thu, Dec 29, 2016 at 07:21:41PM +0100, Jean-Francois Dockes wrote: > > Xapian 1.2 supports a query like: > > > > (A OR B) NEAR (C OR D) > > > > and distributes the factors to create something like: > > > > (A NEAR 2 C) OR (B NEAR 2 C) OR (B NEAR 2 C) OR (A NEAR 2 C) > > > > Xapian 1.4 rejects such

...s, and the summary is supposed to be the sentence where the queried term appears in the document. However, I'm not sure about where to start. I mean, should I call the class of XapianDocument and search through the termlist of each document in the Mset or it'll be better if I begin with the positionlist of the term to get it located in each document? Any suggestion and clues are welcome! Much thanks! Best, Shen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20110420/0dd287b1/attachment.ht...

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8351 > Date: 2007-04-23 01:44:44 +0100 (Mon, 23 Apr 2007) > > Log message (2 lines): > backends/flint/flint_version.cc: Update the flint format version > since older flint versions can't read compressed tags. Am I correct in assuming that this means that when

...itations: * Only OP_OR subqueries are handled. I think supporting these would be a useful step forward by itself, and AIUI it's all you actually need. * Currently the OP_OR subqueries can only have two subqueries of their own. Lifting this restriction needs a bit of work on the new OrPositionList class - the old patch used a series of pairwise OrPositionList objects, but the new patch needs a single one instead - the class needs reworking to handle that. So I think the second limitation needs addressing, and of course any bugs resolving. I can't promise anything re schedule,...

...not an issue > that most users will be concerned with...). Another case for https://trac.xapian.org/ticket/508 I think. > > * Currently the OP_OR subqueries can only have two subqueries of their own. > > Lifting this restriction needs a bit of work on the new > > OrPositionList class > > - the old patch used a series of pairwise OrPositionList objects, but the > > new patch needs a single one instead - the class needs reworking to handle > > that. > > > > So I think the second limitation needs addressing, and of course any bu...

...term may be transformed by synonym expansion into: (filesystem OR (file PHRASE system)) NEAR otherterm > > > * Currently the OP_OR subqueries can only have two subqueries of > > > their own. Lifting this restriction needs a bit of work on the > > > new OrPositionList class > > > - the old patch used a series of pairwise OrPositionList > > > objects, but the > > > new patch needs a single one instead - the class needs reworking > > > to handle that. > > > > > > So I think the second...