search for: positionlists

I've just noticed that new indexes no longer have position.{DB,baseA,baseB} files, all previous indexes (I roll indexes every week using xapian-compact) have the position files. The index seems to work but it is returning some odd results, for example if I run a query with the phrase "machine learning" it mostly returns documents containing "machine learning" but it also

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"),

...queries of the NEAR one. I tested the patch and it does seem to answer my selfish needs... > I can't promise anything re schedule, but hopefully we can sort this out > fairly soon. At least the solution for what's missing now is fairly clear - > we probably want to put the sub-positionlists into a min heap. See, you lost me with the last phrase, and that's why it's better that I don't get into Xapian-core internals :) Anyway it's good enough to know that a patch exists which will hopefully make its way into 1.4.x, meaning that I have no need to work on a bad applicat...

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

Hi everyone, I'm trying to build a summary of each document within the search results, 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

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

...ng to handle that. So I think the second limitation needs addressing, and of course any bugs resolving. I can't promise anything re schedule, but hopefully we can sort this out fairly soon. At least the solution for what's missing now is fairly clear - we probably want to put the sub-positionlists into a min heap. Cheers, Olly

...d OR searching) But I've just pushed an update which will handle this. > > I can't promise anything re schedule, but hopefully we can sort this out > > fairly soon. At least the solution for what's missing now is fairly clear - > > we probably want to put the sub-positionlists into a min heap. > > See, you lost me with the last phrase, and that's why it's better that I > don't get into Xapian-core internals :) A heap is a datastructure which is good for merging ordered lists, and a min-heap just means that the tip of the heap is the smallest entry...

...sage was gone, and that the results appeared reasonable. > > > I can't promise anything re schedule, but hopefully we can sort > > > this out fairly soon. At least the solution for what's missing now > > > is fairly clear - we probably want to put the sub-positionlists > > > into a min heap. > > > > See, you lost me with the last phrase, and that's why it's better that I > > don't get into Xapian-core internals :) > > A heap is a datastructure which is good for merging ordered lists, and > a min-heap just...