[Xapian-discuss] Xapian 1.0.7-3.1 (python libs) : can't find anything
cedric.jeanneret at camptocamp.com
Tue Apr 21 13:18:35 BST 2009
Thanks for your quick answer. With delve, I saw there's a "little" problem indeed.
In fact, my system is a bit tricky, and maybe indexes don't really like it:
omindex indexes data on server A, and my xapian search engin is on server B... so B catches A indexes (with rsync) each 2h and put them locally.
So, when I used delve on "source" index, it works. But when I use it on "target" index, it can't find my word...
Fileserver's index is lanched once a day (at about 1 o'clock), so the xapian engine should have a complete index at about 5 o'clock...
Any idea why I lose index informations while rsync-ing them ?
On Tue, 21 Apr 2009 12:25:25 +0100
Richard Boulton <richard at lemurconsulting.com> wrote:
> First, take a look at http://trac.xapian.org/wiki/FAQ/NoMatches . In
> particular, the part about using delve to look at your DB.
> It's hard to guess what exactly is going on without an actual example of a
> document which should be returned, and the search entered to search for it;
> if I were you, I'd use delve to display the terms in a document, and then
> try and build a query which should return that document. You can display
> the exact query used from python by doing "print str(query)".
> As a total guess, I'd guess that the problem you're coming against is with
> stemming; perhaps when you tried enabling french stemming you didn't do it
> correctly: could you paste the code you used to try this? Note that you'll
> need to call set_stemmer on the queryparser, and then call
> set_stemming_strategy(STEM_SOME) to match omindex's stemming strategy.
Cédric Jeanneret | System Administrator
021 619 10 32 | Camptocamp SA
cedric.jeanneret at camptocamp.com | PSE-A / EPFL
More information about the Xapian-discuss