zeitgeist team mailing list archive
-
zeitgeist team
-
Mailing list archive
-
Message #04001
[Bug 843668] Re: Blowing Xapian max term length corrupts index
This bug was fixed in the package zeitgeist-extensions - 0.0.12-0ubuntu1
---------------
zeitgeist-extensions (0.0.12-0ubuntu1) oneiric; urgency=low
* New upstream release:
- fts can SIGSEGV ZG during reindex (LP: #617309)
- zeitgeist-daemon crashed with RuntimeError in _check_index():
basic_string::assign (LP: #839740)
- Blowing Xapian max term length corrupts index (LP: #843668)
- Can't recover from FTS index corruption (LP: #705944)
-- Didier Roche <didrocks@xxxxxxxxxx> Thu, 08 Sep 2011 11:25:16 +0200
** Changed in: zeitgeist-extensions (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/843668
Title:
Blowing Xapian max term length corrupts index
Status in Zeitgeist Extensions:
Fix Released
Status in “zeitgeist-extensions” package in Ubuntu:
Fix Released
Bug description:
Xapian has a (not very well documented) max term length of 245 bytes.
See fx. http://xapian.org/docs/omega/termprefixes.html. For some
reason this is not always gracefully handled inside Xapian and busting
that limit may occasionally corrupt the index.
This is reproducible by indexing long URLs (at least 245 bytes long).
We already had a cap at 2000 characters, but that was apparently not
good enough.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist-extensions/+bug/843668/+subscriptions
References