search for: unserialising

> 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 it to > create the correct Weight object (broadly similar to how

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

...ng scheme as a intermediate step to implementing the support for Piv+ normalization. All tests pass. But I'm running into some issues with Piv+ normalization. In the Piv+ formula , there are two parameters (s and delta) that control the weight assigned. I think the way I'm serialising and unserialising these parameters has some issues which is causing a few errors, http://pastebin.com/yCyuvF1X. Any suggestion is appreciated! Also, I was wondering if we want to have pivoted normalization weighting as a separate weighting scheme in Xapian as it will make a way to add support of different variatio...

...could be something else, depending on what you're > trying to do. I'm trying to unserialise normalization strings (e.g. "nfn", "nbsl" etc.) along with the new double parameters (s and delta) but it isn't turning out to be smooth because there's no method for unserialising strings in serialise-double.h Although, doing just const string normals = ptr++; or, const string normals = static_cast<const string>ptr++; fixes compile errors. But tfidfweight3 test case is failing with remote backends :- $ ./runtest gdb ./apitest -v tfidfweight3 Running test: tfidfwei...

On Mon, Apr 10, 2017 at 11:47:36PM +0530, Vivek Pal wrote: > > No, use Xapian::Registry to find the weighting scheme from the name > > like how Weight::unserialise() does (otherwise every caller would need > > code similar to that above). > > Okay, I looked into Xapian::Registry and it seems you are referring to using > the get_weighting_scheme method? (which expects a

On Sat, Apr 08, 2017 at 09:11:22PM +0100, James Aylett wrote: > On 8 Apr 2017, at 19:15, Vivek Pal <vivekpal.dtu at gmail.com> wrote: > > >> and the details of which weighting schemes were available in which version > >> isn't a key part of the $set command itself. > > > > Do you suggest dropping that piece of information out? Since the reason behind

...> trying to do. > > > > I'm trying to unserialise normalization strings (e.g. "nfn", "nbsl" > etc.) > > along with the new double parameters (s and delta) but > > it isn't turning out to be smooth because there's no method for > > unserialising strings in serialise-double.h > > Serialising it about round-tripping numbers through strings. You > shouldn't need to serialise a string; you don't even have to worry > about encoding with those strings, since they're all covered by ASCII > anyway. > > > Althoug...

Hi all, We've struck a problem when using remote queries and hoping someone can offer some guidance. I haven't managed to get a C++ reproduction in the test suite, but I have got a demo that fails using Python: import xapian db = xapian.remote_open('localhost', 8100) qp = xapian.QueryParser() qp.set_database(db) query = qp.parse_query('test') enq =

Hi, Do the serialise method of Document and Query produce a valid utf8 string? My problem is with the Node.JS binding. I serialise an object, convert the string to a javascript string, convert the javascript string to a std string and then try to unserialise. The error I get from Xapian is "Bad encoded length: no data". Thanks, Marius -------------- next part -------------- An HTML

Ok, but suppose I have a complex query, something like "(a OR b) AND NOT c OR ##". Do I have to parse the query by myself? > Date: Mon, 4 May 2015 03:03:24 +0100 > From: olly at survex.com > To: lautaromedrano at hotmail.com > CC: xapian-discuss at lists.xapian.org > Subject: Re: [Xapian-discuss] Make Xapian accept all characters > > On Sun, May 03, 2015 at

> It may be worth splitting that part of the $set documentation out into its > own section somehow, because it's getting a bit long - Undoubtedly; $set command has the longest section on the documentation page :) But it would be hard splitting that up because the documentation is organised in a way that each command is really contained in its own specific section. > and the details

I am trying to compile pwlib in order to get h323 support working. Most of the compile is fine except it falls over at the point below. Does anyone have a solution? Thanks Johan make[2]: Entering directory `/root/pwlib/tools/asnparser' g++ -o obj_linux_x86_r/asnparser -Wl,--gc-sections -s -L/root/pwlib/lib ./obj_linux_x86_r/asn_grammar.o ./obj_linux_x86_r/asn_lex.o

Hello, I have two ActiveRecord classes. One is Route the other is Waypoints. I have constructed an XML representation so I can use AJAX to create a Route with all waypoints in a single create call to RouteController. When I call Route.from_xml(xmlString) it is not returning an object - it''s leaving the object (@route) nil, but not erroring. Any ideas? Here''s some code:

Olly Betts <olly at survex.com> wrote: > On Fri, Aug 21, 2020 at 09:06:59AM +0000, Eric Wong wrote: > > Going back to the "prioritizing aggregated DBs" thread from > > February 2020, I've got 390 Xapian shards for 130 public inboxes > > I want to search against(*). There's more on the horizon (we're > > expecting tens of thousands of public

Going back to the "prioritizing aggregated DBs" thread from February 2020, I've got 390 Xapian shards for 130 public inboxes I want to search against(*). There's more on the horizon (we're expecting tens of thousands of public inboxes). After bumping RLIMIT_NOFILE and running ->add_database a bunch, the actual queries seem to be taking ~30s (not good :x). Now I'm