search for: icginc

...:xapian-discuss at lists.xapian.org> Subject: Re: [Xapian-discuss] Converting MySQL database to Xapian On Fri, Apr 26, 2013 at 2:22 PM, James Aylett <james-xapian at tartarus.org<mailto:james-xapian at tartarus.org>> wrote: > On 26 Apr 2013, at 14:12, Michael Lewis <mal at icginc.com<mailto:mal at icginc.com>> wrote: > >> My first question is: On ServerY and the Web Server how do I set-up Xapian for access. In the PHP code do I have to actually know where the databases are located or is that the function of some kind of stub database? In an ideal world t...

I was looking for performance comparisons. I just found this link (http://blog.inoi.fi/2010/10/migrating-from-xapian-to-elasticsearch.html <http://blog.inoi.fi/2010/10/migrating-from-xapian-to-elasticsearch.html>). This was write on 2010. Could someone comment it ? Is There some truth in what he said? I hate java, and didn?t want to back to java search engines...

I am looking for some guidance on converting a large MySQL database to Xapian. The current structure is that the database is broken up into 160 "sub-databases". There are 50,000 or so records in each stub database. Each record has content that I am full-text indexing. The average size of the text is about 59k characters. The database is broken up into sub-databases because the MySQL

I've done a number of small projects (<1 mil) docs w xapian. However when our needs grew to a couple of hundred million docs no go. Index times get insanely slow very quickly We add about 250,000 docs a day. You can play games with switching indexes during updates and multiple remote dDBs. But why. Using ES we index 1000 new docs in 4 seconds. Our search times are subsecond in most

I have written a very simple function to return the match count based on the simplesearch.cc code. It fails with a seg fault. The relevant code is: -------------------- int ftQuery(char* qs, const char* dbname,char* results, int msize) { long docid; char* op; char fullDB[1024]; string queryString;