[Xapian-tickets] [Xapian] #442: Add support for mapping field names to differing term prefixes across multiple databases
Xapian
nobody at xapian.org
Mon Jan 9 10:41:05 GMT 2012
#442: Add support for mapping field names to differing term prefixes across
multiple databases
-------------------------+--------------------------------------------------
Reporter: richard | Owner: olly
Type: enhancement | Status: closed
Priority: normal | Milestone: 1.2.x
Component: Library API | Version: SVN trunk
Severity: normal | Resolution: wontfix
Keywords: | Blockedby:
Platform: All | Blocking:
-------------------------+--------------------------------------------------
Changes (by olly):
* status: new => closed
* resolution: => wontfix
Comment:
This still seems like it would be opening a can of worms, even 2 years
later. There are likely
to be a lot of awkward issues to resolve - e.g. I can see the ordering of
converted terms being interesting.
Although we don't have the B-tree key prefix compression completed yet, I
think that's a better way to expend implementation effort - it also would
reduce database size significantly in general, and that would add
complexity only to the lower levels of the backend code, rather than
touching a lot of areas of the code, and it wouldn't require any user API
additions.
Yes, that's ''"relying on as-yet unimplemented and unproven database
storage improvements"'',
but then the approach proposed here is relying on as-yet unimplemented and
unproven changes
to how Xapian maps terms to keys in databases.
If we're going to decouple the field and the term rather than adding a
prefix like we currently
do, let's do it properly and make the appropriate API changes. This
probably won't be fully
backwardly compatible, but we can make this change in Xapian 2.0.
So I'm going to mark this idea as "won't fix".
--
Ticket URL: <http://trac.xapian.org/ticket/442#comment:2>
Xapian <http://xapian.org/>
Xapian
More information about the Xapian-tickets
mailing list