search for: inmemory

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 thread2 because WritableDatabase object isn't thread-safe. And...

...0 Olly Betts <olly at survex.com>: > On Thu, Jun 19, 2014 at 10:52:13PM +0800, Yanxiong Lu wrote: > > 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()); > > While the inmemory backend is handy for some things, in its current > incarnation some operations really aren't very time efficient, and it > doesn't even try to be very space efficient. > > The longer term plan is to replace it, probably sharing code with th...

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 for testing purposes, so it isn't coded with efficiency in mind and...

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: <http://lists.xapian.org/pipermail/xapi...

...ached-databases rm -rf .chert .glass .multichert .multiglass .replicatmp .stub Command:./runtest ./apitest --verbose topercent2 Output: Running test './apitest --verbose topercent2' under eatmydata and valgrind Running tests with backend "none"... Running tests with backend "inmemory"... Running test: topercent2... Command: ls -R .chert Output: .chert: db=apitest_simpledata .chert/db=apitest_simpledata: flintlock You ought to have a database in .chert/db=apitest_simpledata - if so, > then checking it would be interesting (again send the output): > > ../bin/xapi...

...at was used to open the database. For a remote (TCP) database, it would return a string indicating the host and port that the database is at (probably in a pseudo URL form something like "remotetcp://host:port/"), and something similar for a remote progsrv database. Not sure what an inmemory one would return... Alternatively, databases could have a new "set_name()" method which sets the name to return (possibly with something like the above as the default) to avoid having to do long string compares to work out which database a document came from. This would also be usef...

...med 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 test cases. > > > Running tests with backend "inmemory"... > > Running test: topercent2...FAIL: apitest > > > Running test './queryparsertest' under eatmydata and valgrind > > Running test: qp_spell1...FAIL: queryparsertest > > > Running test './termgentest' under eatmydata and valgrind > > Runni...

...t;... make check-TESTS make[5]: Entering directory `/home/saad/GitProjects/xapian/build/xapian-core/tests' Running test './apitest' under eatmydata and valgrind Running tests with backend "none"... ./apitest backend none: All 85 tests passed. Running tests with backend "inmemory"... Running test: topercent2...FAIL: apitest Running test './internaltest' under eatmydata and valgrind PASS: internaltest Running test './stemtest' under eatmydata and valgrind The random seed is 42 Please report the seed when reporting a test failure. Running tests with arm...

...ls 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 <- ls() inMemory <- ls(1) inBoth <- inFile[inFile %in% inMemory] for(thing in inBoth){ if(identical(get(thing,1),get(thing))){ cat(paste("Object :",thing," identical\n")) }else{ cat(paste("Object :",thing," changed\n")) } } li...

...ake remove-cached-databases" and run "./runtest ./apitest --verbose topercent2" the second time then the output is " Running test './apitest --verbose topercent2' under eatmydata and valgrind Running tests with backend "none"... Running tests with backend "inmemory"... Running test: topercent2... DatabaseOpeningError: Couldn't detect type of database ./apitest backend inmemory: 0 tests passed, 1 failed. Running tests with backend "glass"... Running test: topercent2... DatabaseOpeningError: Couldn't detect type of database ./apitest back...

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

...that if you configure git master with --disable-gpl-libxapian then you'll get a build with some features disabled which only contains code that we should be able to relicense (NB the code hasn't actually been relicensed yet). This option currently disables the following: * glass backend * inmemory backend * remote backend * replication The only backend you get is the new "honey" backend which currently only supports reading. To create a honey database, you currently need to use a full build of xapian-core, build a glass database, and then use xapian-compact to convert it to honey...

...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 `/home/mcam/xapian-core-0.9.1/backends/inmemory' if /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../common -I../../include -Wall -W -Wredundant-decls -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-multichar...

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 -- /--------------------------------------------------------------------------\ James Aylett...

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

...glass_spellingwordslist.o backends/glass/.libs/glass_synonym.o backends/glass/.libs/glass_table.o backends/glass/.libs/glass_termlist.o backends/glass/.libs/glass_termlisttable.o backends/glass/.libs/glass_valuelist.o backends/glass/.libs/glass_values.o backends/glass/.libs/glass_version.o backends/inmemory/.libs/inmemory_alltermslist.o backends/inmemory/.libs/inmemory_database.o backends/inmemory/.libs/inmemory_document.o backends/inmemory/.libs/inmemory_positionlist.o backends/multi/.libs/multi_alltermslist.o backends/multi/.libs/multi_postlist.o backends/multi/.libs/multi_termlist.o backends/multi/...

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 -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -W...

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,

...kiwix.org > <mailto:kelson at kiwix.org>> wrote: > > 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 -Wall -W > -Wredundant-decls -Wp...

...olutions. I tried the following: - changed $(srcdir)/include/xapian.h into $(srcdir)/include/xapian.h.in - added the following lines somewhere (namely, line 51) in xapian.h.in: ---8-<------------- // Backends #define XAPIAN_BACKEND_MUSCAT36 #define XAPIAN_BACKEND_QUARTZ #define XAPIAN_BACKEND_INMEMORY #define XAPIAN_BACKEND_REMOTE ---8-<------------- - added the following to configure.ac, at line 374 (to have $build_* set): ---8-<------------- dnl @@MODIFIED@@ - Franz dnl Remove unsupported backend #defines from xapian.h.in and output xapian.h AC_MSG_CHECKING([for backends to exclude i...