search for: unimplementederror

...wing Python extract: >>> from xapian import * >>> qp = QueryParser() >>> qp.set_default_op(Query.OP_PHRASE) >>> print qp.parse_query('John Smith-Jones') Traceback (most recent call last): File "<stdin>", line 1, in <module> xapian.UnimplementedError: Can't use NEAR/PHRASE with a subexpression containing NEAR or PHRASE I'm using the latest release (1.2.6). Are there any plans to implement this functionality, or does anyone have a patch for the query parser that would fix this particular issue? If not, I guess a good workaround on my s...

Olly Betts writes: > On Thu, Jan 12, 2017 at 07:53:21PM +0100, Jean-Francois Dockes wrote: > > > Recoll also supports multi-word synonyms which could potentially > > generate PHRASE subqueries inside NEAR queries, but this > > understandably already did not work with 1.2, so the multi-word > > expansions are only used when proximity is not involved (by the way,

On Sun, Apr 09, 2017 at 11:34:07PM +0530, Vivek Pal wrote: > > Each scheme already has a human-readable name, and Xapian::Registry > > can map that to an "examplar" object of the right type, so we > > could take a string like "bm25 1 0.8", see the first word is "bm25" > > and get a BM25Weight object, then call parse_params("1 0.8") on

...t; > > > (text OR texts) NEAR (search OR searches OR searched OR searching) > > > > But I've just pushed an update which will handle this. > > Ok, I hadn't even noticed the limitation. Dit it silently truncated the > OR list ? It would throw Xapian::UnimplementedError. > But, actually, so does the previous version (commit 389dfb319a66), which > explains why I had not understood what the limitation was. > > Both versions also work fine with "floor floor floor"p: > > (floors OR flooring OR floored OR floor) NEAR 13 > (floors OR fl...

On Sun, Sep 30, 2018 at 09:05:25AM -0300, David Bremner wrote: > if (str.find (' ') != std::string::npos) > query_str = '"' + str + '"'; > else > query_str = str; > > return parser.parse_query (query_str, NOTMUCH_QUERY_PARSER_FLAGS, term_prefix); I wouldn't recommend trying to generate strings to feed to

...admin and away at the moment. I'll resend the checksums signed once we sort that out. Expect to see GPG signed release announcements in the future. This release fixes a number of bugs and improves efficiency in a few cases. Notable changes in this release: * Enquire::get_mset() now throws UnimplementedError if there's a percentage cutoff and sorting is primarily by value - this has never been correctly supported and overall it seems better to warn people than give incorrect results. However, this change means that existing applications will now fail visibly in some cases when they might h...

Olly Betts <olly at survex.com> wrote: > On Fri, Aug 18, 2023 at 10:41:52AM +0000, Eric Wong wrote: > > Olly Betts <olly at survex.com> wrote: > > > While the match is running, get_mset(2000, 1000) needs to track > > > 3000 entries so this won't reduce your heap usage (at least not > > > peak usage). > > > > > > Is the heap

Hi Everybody, Here is the first version of my match for an ExternalPostList, it should apply cleanly to 0.9.5 and 0.9.6. You can use it by first implementing an ExternalPostingSource, then creating a new Query object passing a reference an instance of your implementation to the constructor, see query.h. The ExternalPostingSource implementation is reference counted, so when its no

...you are referring to using > the get_weighting_scheme method? (which expects a string e.g. "bm25" i.e. the > name of a weighting scheme.) Yes, you pass it a string and it gives you the registered object with that name. > And, Weight::unserialise() looks like throwing a Xapian::UnimplementedError > error. I wonder if you meant the same method? That's the default implementation - each subclass overrides that with an actual implementation (at least if it wants to work with remote databases). > > The code in omega would just be: > > > > enq.set_weighting_scheme(Xap...

.../man3/Search::Xapian::RangeError.3pm Manifying blib/man3/Search::Xapian::BM25Weight.3pm Manifying blib/man3/Search::Xapian::WritableDatabase.3pm Manifying blib/man3/Search::Xapian::SerialisationError.3pm Manifying blib/man3/Search::Xapian::DatabaseCreateError.3pm Manifying blib/man3/Search::Xapian::UnimplementedError.3pm Manifying blib/man3/Search::Xapian::InvalidArgumentError.3pm Manifying blib/man3/Search::Xapian::DatabaseModifiedError.3pm Manifying blib/man3/Search::Xapian::ValueIterator.3pm Manifying blib/man3/Search::Xapian::Error.3pm Manifying blib/man3/Search::Xapian::DatabaseLockError.3pm Manifying blib...

...< query.serialise() << endl; + logfile.close(); + */ + LOGCALL(MATCH, MSet, "Enquire::Internal::get_mset", first | maxitems | check_at_least | rset | mdecider | matchspy_legacy); if (percent_cutoff && (sort_by == VAL || sort_by == VAL_REL)) { throw Xapian::UnimplementedError("Use of a percentage cutoff while sorting primary by value isn't currently supported"); @@ -701,6 +714,7 @@ const RSet & rset, int flags, double k, const ExpandDecider * edecider, Xapian::weight min_wt) const { + cout << "In Enquire::Interna...

My code is not on Github. I am using the tarball as of now. The following it the error that occurred: http://pastebin.com/cVJrjUZX On Sun, Apr 13, 2014 at 8:16 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:37, Pallavi Gudipati <pallavigudipati at gmail.com> > wrote: > > > A linker error is encountered even after following the above