search for: numbervaluerangeprocessor

Displaying 4 results from an estimated 4 matches for "numbervaluerangeprocessor".

2008 Jan 21
2
NumberValueRangeProcessor documentation
I think we want to apply the following patch to make the NumberValueRangeProcessor documentation (a) make sense, and (b) accurate: ---------------------------------------------------------------------- --- include/xapian/queryparser.h (revision 9993) +++ include/xapian/queryparser.h (working copy) @@ -213,7 +213,7 @@ * * For example, if str_ is "$...
2015 Sep 09
2
custom ValueRangeProcessor in Perl?
...orkaround (using the Chronic date parsing library). Below are my attempts at making my own ValueRangeProcessor class. Thanks in advance for any help or pointers you can provide. Disclaimer: I am not knowledgeable in XS, SWIG, C++, or experienced in using Xapian at all. # Try #1 with subclassing NumberValueRangeProcessor: package PublicInbox::Search::DateVRP1; use strict; use warnings; use base 'Search::Xapian::NumberValueRangeProcessor'; sub new { my ($class, @args) = @_; Search::Xapian::NumberValueRangeProcessor::new($class, @args); } # doesn't seem to get called sub process_value_rang...
2018 Jul 19
1
choosing between probabilistic and boolean prefixes for terms
...rser $qp = Search::Xapian::QueryParser->new; $qp->set_default_op(OP_AND); $qp->set_database($self->{xdb}); $qp->set_stemmer($self->stemmer); $qp->set_stemming_strategy(STEM_SOME); $qp->set_max_wildcard_expansion(100); $qp->add_valuerangeprocessor( Search::Xapian::NumberValueRangeProcessor->new(YYYYMMDD, 'd:')); $qp->add_valuerangeprocessor( Search::Xapian::NumberValueRangeProcessor->new(DT, 'dt:')); In any case, all the code is available via: git clone https://public-inbox.org/public-inbox
2007 Jun 23
1
Test failures
Tinderbox is showing failures in Search::Xapian on atreus with g++ 4.1 (which looks like tests out of date at a *very* cursory examination, and in any case everyone should know about); I'm also getting different test failures on the same system -- valgrind (I assume) is finding potential memory leaks for every test against the remotetcp backend. (Incidentally, I've just installed