Displaying 10 results from an estimated 10 matches for "docnotfounderror".
2007 Jul 24
1
Xapian::DocNotFoundError on replace_document? (Called from Search::Xapian)
Hello,
I'm using Xapian 1.0.2 (flint) and matching Search::Xapian.
I'm getting:
terminate called after throwing an instance of
'Xapian::DocNotFoundError', which dumps core.
at first it was after adding my 2nd document (to an empty db, although
I don't know if that has any bearing) to the database with a
replace_document() call.
I shifted the first document off the processing stack (moved the file
away), and then it crashed doing a replac...
2010 Feb 18
2
xapian.DocNotFoundError: regression?
Hello,
I've installed xapian-core 1.1.3 and xapian-bindings 1.1.4 from the
tarballs announced by Olly the other day. With these versions,
Enquire.get_mset() seems to consistently be raising
xapian.DocNotFoundError.
I've attached a small test case which reproduces this. The same test
case works fine with 1.0.16 (not the latest 1.0.x, but it's what I had
installed).
Program output with 1.1.3 (core) / 1.1.4 (bindings):
tack at orion:~$ rm -rf xapdb/; python xaptest.py
Traceb...
2007 Mar 03
1
Error handling in the bindings
...standard SWIG error types: for example, if
any Xapian::DatabaseError exception is raised, SWIG will use its
standard SWIG_IOError error type to report the error.
In Python, this leads to code like the following:
try:
db.get_document(1)
except RuntimeError, e:
if str(e).startswith('DocNotFoundError:'):
# Handle a DocNotFoundError
(Incidentally, the error raised in python for this actually is a
RuntimeError, not an IOError as I would have expected from reading the
SWIG code, but that's not a major issue.)
For Python, it would be much nicer to have the full exception heirar...
2007 Mar 03
1
Error handling in the bindings
...standard SWIG error types: for example, if
any Xapian::DatabaseError exception is raised, SWIG will use its
standard SWIG_IOError error type to report the error.
In Python, this leads to code like the following:
try:
db.get_document(1)
except RuntimeError, e:
if str(e).startswith('DocNotFoundError:'):
# Handle a DocNotFoundError
(Incidentally, the error raised in python for this actually is a
RuntimeError, not an IOError as I would have expected from reading the
SWIG code, but that's not a major issue.)
For Python, it would be much nicer to have the full exception heirar...
2015 Mar 11
2
stub-file and get_doccount
Hello,
i switched from one big index to a stub file with many indexes and running
into a problem.
i have a tool to fetch a random document via:
get_doccount
random id up to get_doccount
get_document with that id
after changing to stub file this failes. Is there a nice way to get a
random document from a stub file?
?MfG?
Felix Ostmann
2016 Jan 08
2
Strange index consistency issue
...ist of IDs, one of
which was 6. I then ran "delve -r 6 ./xapiandb" and got a long list of
terms, which included 'term' and seemed to be reasonable for a document I
then ran "delve -r 6 ./xapiandb -d" and got the following:
Data for record #6:
Error: DocNotFoundError: Document 6 not found
And the output from xapian-check:
============
record:
baseB blocksize=8K items=84507 lastblock=3379 revision=157 levels=2 root=12
B-tree checked okay
record table structure checked OK
termlist:
baseB blocksize=8K items=169014 lastblock=24090 revision=157 levels=2 root=5
B-...
2007 Jun 19
2
Deleted documents not deleted
I seem to be seeing cases where I call db.delete_document(somedocid) with
no error, then flush() and delete the database object, but the document is
still there after process exit. The write lock is normally deleted, so it
appears that the database close finished normally.
If I then then call delete_document(somedocid) from another
command/process, this time it goes away.
I've been seeing
2016 Jan 09
0
Strange index consistency issue
...as 6. I then ran "delve -r 6 ./xapiandb" and got a long list of
> terms, which included 'term' and seemed to be reasonable for a document I
> then ran "delve -r 6 ./xapiandb -d" and got the following:
>
> Data for record #6:
>
> Error: DocNotFoundError: Document 6 not found
Hmm, if you're getting it with '-d' there, that makes me suspect a
missing record table entry.
> To repeat, the issue here is not that the index is corrupted, but that
> xapian-check does not see it. Is there some more thorough test which could
> be run...
2010 Mar 07
2
"Value in posting list too large" error with 1.1.4 (chert and brass, not flint)
...4. Periodically also does queries on the database
With 1.1.4, with certain document sets (basically a particular mail
folder of mine), Enquire.get_mset() sometimes (but not always) triggers
a "RangeError: Value in posting list too large" error. Once this
happens, occasionally I also see DocNotFoundError.
After the indexing completes and a final explicit flush() is called and
the program exits, xapian-check reports no errors found, so at least the
database seems consistent on disk.
What's interesting is that if I set XAPIAN_FLUSH_THRESHOLD to be a value
larger than the document set size (and...
2011 Apr 21
1
Installing Search::xapian
...ying blib/man3/Search::Xapian::RuntimeError.3pm
Manifying blib/man3/Search::Xapian::TermIterator.3pm
Manifying blib/man3/Search::Xapian::TradWeight.3pm
Manifying blib/man3/Search::Xapian::DatabaseCorruptError.3pm
Manifying blib/man3/Search::Xapian::BoolWeight.3pm
Manifying blib/man3/Search::Xapian::DocNotFoundError.3pm
Manifying blib/man3/Search::Xapian::LogicError.3pm
Manifying blib/man3/Search::Xapian::Stem.3pm
Manifying blib/man3/Search::Xapian::PostingIterator.3pm
Manifying blib/man3/Search::Xapian::PositionIterator.3pm
Manifying blib/man3/Search::Xapian::MultiValueSorter.3pm
Manifying blib/man3/Search::X...