search for: valuerangeprocessors

I want to set a variable number and type of ValueRangeProcessors at run time based on a configuration file. But I seem to be running into (what I think is) a C++ scope issue. I tried just a simple test to see if I could add 5 VPs in a loop. Xapian::QueryParser qparser; Xapian::Query query; int vp = 0; while(vp < 5) { Xapian::StringV...

Hello, I'm using the XS Perl bindings packaged with Debian stable and am interested in implementing my a custom ValueRangeProcessor (using DateTimeX::Easy for human-friendly date parsing) Unfortunately, I'm not sure if it's possible with the add_valuerangeprocessor API via Perl. Reading the XS/*ValueRangeProcessor.xs source files, I'm seeing "process_value_range"

Hi all, I'm getting an error in the smoketest. I'm using latest Swig and Python bindings from SVN-HEAD: File "smoketest.py", line 23, in <module> import xapian File "C:\work\xapian\xapian-SVN\xapian-core\win32\Release\Python\xapian.py", line 2099, in <module> ValueRangeProcessor.__call__ = ValueRangeProcessor.__call AttributeError: type

Hi all, I found that the figure returned by MSet::get_matches_estimated() varies depending on how results are to be sorted. For instance, in my index, value 4 contains date and time in the format "yyyymmddhhmmss". For the same query, the number of results will be estimated to 20000+ when results are first sorted by date and time with set_sort_by_value_then_relevance(4) and to only 100

(xapian 1.0.1) Should TermGenerator in the PHP4 bindings be called XapianTermGenerator? Thanks, Tim.

I'm happy to be able to announce that Xapian 1.3.6 is now available. Please note that 1.3.x releases are development releases - they are made to encourage earlier and wider use and testing of new and changed code. We're pretty close to a stable 1.4.0 release at this point - there's currently only one ticket still pegged on 1.3.x, which is to sort out some details of the

I've uploaded Xapian 1.0.11 (including Search::Xapian 1.0.11.0), which as usual you can download from: http://xapian.org/download Starting from this release, I'm going to include SHA1 checksums of the released files in the release announcement. For 1.0.11 these are: 480fd99617975c1aaf9127cd7c7166bc05d07eb1 Search-Xapian-1.0.11.0.tar.gz 217c7fb1754d0aeaf82c3ab83d5ec0881099bb61

Hi, I'm using xapian with c# and mono and i'm having a segfault in get_weight. When i print the index variable, the value is clearly too high. I think something write over it. Do you have any idea on how i could trace the beginning of the segmentation fault ? Thanks, -- Yann