search for: inmemori

hi, Why xapian don't support memory index/search ? I know there is a method can create memory datebase, like this: Xapian::WritableDatabase db(Xapian::InMemory::open()); *But, if i use these in multithread program, i need create many datebases!!* Xapian::WritableDatabase db1(Xapian::InMemory::open()); //used in thread1 Xapian::WritableDatabase db2(Xapian::InMemory::open()); //used in

There may be some solutions?for example class XAPIAN { *static* int InitDatabase(); //for reading only, do not need lock, but if writing use lock int Search(); //safe in one object, do not need lock }; XIPIAN xp[ THREAD_NUM ]; one thread use one object, they use one database. these can be in memory with one database. 2014-06-24 20:48 GMT+08:00 Olly Betts <olly at survex.com>:

I've just added a feature test for the new WritableDatabase methods - replace_document() and delete_document() with a unique term. This initially failed for inmemory due to bugs in the backend. They weren't trivial to fix and my initial attempt at a fix caused other tests to fail. I've come to the conclusion that the code there probably should be retired. It was written early on

Hi olly, I rewrote the test for PL2 after adding code to deal with negative weights. It passes on all backends other than inmemory . I see a different value of weight for inmemory backend. The code to calculate the lower bound is implemented in init().Please can I get some help with this ? -Regards -Aarsh -------------- next part -------------- An HTML attachment was scrubbed... URL:

---------- Forwarded message ---------- From: Saad Ahmed <ch.saad.ahmed at gmail.com> Date: 3 February 2015 at 21:10 Subject: Waiting for Reply regarding "TestCases Failure" To: Xapian Development <xapian-devel at lists.xapian.org> I have been waiting for reply regarding any further steps to take. Following are the outputs of commands that you asked me to run. All these

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 9092 > Date: 2007-06-30 15:16:16 +0100 (Sat, 30 Jun 2007) > > Log message (2 lines): > api/omdocument.cc,common/document.h,include/xapian/document.h: > Add Xapian::Document::get_docid() method. I was thinking that it would probably be useful to have a

Please find my inline reply. On 26 January 2015 at 06:56, Olly Betts <olly at survex.com> wrote: > On Sun, Jan 25, 2015 at 06:46:26PM +0500, Saad Ahmed wrote: > > I have been able to successfully build the code. But when I run the > > existing testcases (to verify everthing is working fine), It says 3 out > of > > the six testcases fails. Here is the report of the

Hi, I am a student in Pakistan willing to contribute to Xapian. I have been able to successfully build the code. But when I run the existing testcases (to verify everthing is working fine), It says 3 out of the six testcases fails. Here is the report of the test cases. "... make check-TESTS make[5]: Entering directory `/home/saad/GitProjects/xapian/build/xapian-core/tests' Running

Sometimes after playing around in R for a while, I find myself thinking, "What have I done?". Which boils down to "What's the difference between the objects I currently have in my R session and those that were loaded from my .RData when I started R". So I bashed this out in five minutes, just to test the principles. differ <- function(file){ load(file) inFile

> Is that the complete output? Yes it is the complete output against "./runtest ./apitest --verbose topercent2"( after running make remove-cached-databases). I attached the snapshot of the output of commands but the size of the email got bigger than 40kb so i had to place the output as text. If I do not run "make remove-cached-databases" and run "./runtest ./apitest

LGTM. I will commit. On Oct 10, 2012, at 1:20 PM, Shuxin Yang <shuxin.llvm at gmail.com> wrote: > Hi, > > The attached is the fix to radar://11663049. The optimization can be outlined by following rules: > > (select (x != c), e, c) -> select (x != c), e, x), > (select (x == c), c, e) -> select (x == c), x, e) > where the <c> is an integer

This is an update on the current status of the relicensing, but also an opportunity to give feedback. Sorry it's rather long, but I think it's necessary to summarise the situation - there are probably list members who weren't even born at the start of the history of this! Xapian is currently licensed as GPLv2+, but isn't something we actually chose for Xapian, but rather due to a

I'm getting the following error when trying to build xapian. I've tried versions 0.9.1 and 0.9.2, same error. It's a x86 debian box, gcc 4.0.1. It builds fine on my gentoo amd64 box (gcc 3.4.3). Any ideas? Thanks, Alex make[3]: Leaving directory `/home/mcam/xapian-core-0.9.1/backends/flint' Making all in inmemory make[3]: Entering directory

Hi - I've been fixing up the bindings to match the latest API. Should be able to commit later today or tomorrow. The smoketest on PHP isn't working any more, apparently because the inmemory backend isn't accessible (I haven't looked in detail - I fixed them for something I was doing). (Also some more magic iterators for the Python bindings.) J --

Greets, I'm giving a stab at patching the CPAN module to add the missing WritableDatabase::add_spelling and remove_spelling, but need a bit of guidance since I'm coming in cold, and pressed for time (aren't we all). I've modified XS/WritableDatabase.xs and added the two necessary functions, and also added the two basic tests in t/index.t. Compilation completes cleanly, but

Dear All, I've tried to build xapian-core 1.4.3 on MSYS2. It fails with attached error (undefined reference to `exp10'). I think it might be missing an explicit link to 'm'. I'm not able to fix this myself as I do not know autotools sufficiently well, but I hope you might be able to help. Cheers, Mario Emmenlauer -- BioDataAnalysis GmbH, Mario Emmenlauer Tel.

Hi Compilation of 1.3.7 dies with the following configuration: ==================================== ./configure --enable-shared --enable-static --disable-sse --disable-backend-inmemory --disable-backend-remote ==================================== During the compilation I get the following error: ==================================== /bin/bash ./libtool --tag=CXX --mode=link g++ -fshow-column

Hi, The attached is the fix to radar://11663049. The optimization can be outlined by following rules: (select (x != c), e, c) -> select (x != c), e, x), (select (x == c), c, e) -> select (x == c), x, e) where the <c> is an integer constant. The reason for this change is that : on x86, conditional-move-from-constant needs two instructions; however,

$ c++ --version c++ (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 On 20.06.2016 21:55, Kevin Duraj wrote: > Emmanuel, > Which version of C++ compiler are you using? > > $ c++ --version > c++ (GCC) 4.9.3 > Copyright (C) 2015 Free Software Foundation, Inc. > > -Kevin > > > On Mon, Jun 20, 2016 at 6:58 AM, Emmanuel Engelhart <kelson at kiwix.org > <mailto:kelson

A short note: this message comes as a public reply to a discussion about xapian-bindings, that is why it can look a little bit incomplete... however the problem for now was to modify the xapian-core distribution so that there are symbols #defined (or maybe #undefined) to reflect what backends were available in the library. As I said to Olly, I'm a complete newbie at Autotools (and SWIG), so