similar to: Using a subclass of MatchSpy in Python bindings

Hey I?m cleaning up some code at my work place, and it turns out someone had forked Search::Xapian and added MatchSpy bindings for it for one of our internal projects. I was wondering if I should try to extract this as a patch against the current Search::Xapian code, and submit it, or if that is not wanted/wasted effort? It seems to be against 1.2.4.n of Search::Xapian, but I think I should be

On 19 August 2015 at 20:55:32, Olly Betts (olly at survex.com) wrote: On Wed, Aug 19, 2015 at 05:31:31PM +0700, Andreas Marienborg wrote: > If I want to create a patch, should it be against the xapian-bindings > directory/repo? or somewhere else? Against the search-xapian directory of the git repo would be best. Hey, I made a branch from svn/1.2 on github, and tried to forward

Have been working recently on a site that classifies posts using tags in taxonomies, so a post about the Oil spill in the Gulf of Mexico might be tagged 'Subscribers only' (access level), 'Barack Obama' (person), 'Tony Hayward' (person), 'BP' (company), 'Transocean' (company), 'Gulf of Mexico' (location). With some advice from Richard Boulton I

On Tue, Aug 25, 2015 at 10:45:12AM +0700, Andreas Marienborg wrote: > If someone with more XS-exerpience could take a look and provide > some feedback, that would be great. Looks plausible to me. I'd suggest that ~Enquire_perl() just call ref_clear_matchspies(NULL); rather than repeating all its code inline. > I created a pull request[1]. I would like to get the PerlMatchSpy thing

On Wed, Aug 19, 2015 at 05:31:31PM +0700, Andreas Marienborg wrote: > I?m cleaning up some code at my work place, and it turns out someone > had forked Search::Xapian and added MatchSpy bindings for it for one > of our internal projects. I was wondering if I should try to extract > this as a patch against the current Search::Xapian code, and submit > it, or if that is not

Hi colleagues, I have a simple product database indexed with Xapian. Amazing free tool, thanks you developer(s)! I need to have a way to return prices of products in groups, say I have prod prices: 1.01 1.03 10.01 250.44 260.33 I need to get it to return something like: Group 1 = 1.01 ? 1.03 Group 2 = 10.01 etc. Maybe there is something build-in Xapian that can do

Hi everyone, I'm having a problem with xapian (the matchspy branch, with Python bindings) on Solaris 10 / SPARC. Users can run queries for a few hours with no problems, then it returns "inflate failed (invalid code lengths set)" to Python and dumps core. gdb reports: #0 0xfe6dc910 in inflate_table () from /usr/lib/libz.so.1 #1 0xfe6d9d6c in inflate () from /usr/lib/libz.so.1 #2

> I think this is a shining example of how well Xapian works with large > document collections. I was just discussing this with my colleagues here > and one of the issues that came up is that we'd love Xapian to become > really lot more popular but have found that the documentation's a bit > difficult to get into, as is the API. I agree. There are a few gotchas, as well

Hi there, My web app uses Xapian via the PHP bindings. I'm getting this error thrown occasionally when atempting to instantiate a XapianDatabase object for searching. DatabaseCorruptError: Expected block 107 to be level 1, not 0 Here's the line that invokes it: $database = new XapianDatabase(PROJROOT.'/data/xapian/posts'); And my version is xapian-core 1.2.3 with matchspy.

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

Hi all, [ Hopefully announcements like this are appropriate here... ] I've just released version 0.2 of my maildir scanner/search called 'mu': http://www.djcbsoftware.nl/code/mu/ It it's written in C and a bit of C++, and released under the GPL. Thanks for the help I got here, it was quite easy to integrate Xapian, and it works really nice -- a high quality product. Great job!

Hi everyone, I'm having a problem with xapian (the matchspy branch, with Python bindings) on Solaris 10 / SPARC. Users can run queries for a few hours with no problems, then it returns "inflate failed (invalid code lengths set)" to Python and dumps core. gdb reports: #0 0xfe6dc910 in inflate_table () from /usr/lib/libz.so.1 #1 0xfe6d9d6c in inflate () from /usr/lib/libz.so.1 #2

At least it isn't working the way it used to. Code: $db = Search::Xapian::Database->new( $dx ); my $qp = Search::Xapian::QueryParser->new(); my $dbSize=$db->get_doccount(); # $qp->set_stemmer(new Search::Xapian::Stem("english")); # $qp->set_stemming_strategy(STEM_SOME); # $qp->set_default_op($defaultop); my $par =

We are using the --enable-maintainer-mode and will move to git soon. The diff file is attached. *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai http://www.siddhantmutha.com/ <http:/www.siddhantmutha.com/> On Sun, Apr 13, 2014 at 8:26 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:48, Pallavi

Can I use xapian for a search like: 'title' has the phrase "dinner jacket" AND 'color' == BLACK AND 'state' == MA AND 'size' == XL What about faceted search? Thanks

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, we are an email hosting provider and we are looking at xapian to improve our user experience about email search. So we staring to build xapian 1.4.15 on Centos 7 with your xapian-core.spec and move it and the source code in /root/rpmbuild/SPECS and SOURCE, but we have this error after run "rpmbuild -ba": [...] Elaborazione file: xapian-core-devel-1.4.15-1.x86_64 errore: File