search for: valuerangeprocessor

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::String...

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" methods being defined (but I can't fi...

...ing 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 object 'ValueRangeProcessor' has no attribute '__call' This is the very last line in xapian.py, if that's relevant! Cheers Charlie

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.

...this easier). If they are binary packages you should also be aware that 1.3.x comes with no guarantee of ABI stability (code built against 1.3.5 will need rebuilding for 1.3.6). The most substantial change since 1.3.5 is the addition of the Xapian::RangeProcessor class, which will replace Xapian::ValueRangeProcessor (still present, but now deprecated). Xapian::RangeProcessor allows ranges to expand to any Xapian::Query, not just a value range, and provides more flexible grouping. And we've also finally deprecated Xapian::WritableDatabase::flush() - just use commit() instead - it was added in Xapian 1.1.0,...

...; so that it doesn't block unmounting of any partitions and closes any open file descriptors which aren't relating to locking so that if those files are closed by our parent and deleted the disk space gets released right away. * We now keep Python references to Sorter, Stopper, and ValueRangeProcessor objects which get set on other objects to avoid segmentation faults if they go out of scope before the object they are set on does. * Omindex now supports indexing Microsoft Office 2007 formats and XPS files. For a more detailed overview see: http://trac.xapian.org/wiki/ReleaseOverview/1.0.1...

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