[Xapian-tickets] [Xapian] #178: No remote backend support for: spelling correction, synonyms, matchdecider, metadata_keys_begin()

[Xapian]

#178: No remote backend support for: spelling correction, synonyms, matchdecider,
metadata_keys_begin()
----------------------------+------------------------------
 Reporter:  richard         |             Owner:  olly
     Type:  defect          |            Status:  assigned
 Priority:  normal          |         Milestone:  1.4.x
Component:  Backend-Remote  |           Version:  SVN trunk
 Severity:  normal          |        Resolution:
 Keywords:                  |        Blocked By:
 Blocking:                  |  Operating System:  All
----------------------------+------------------------------
Changes (by olly):

 * milestone:  1.3.x => 1.4.x


Comment:

 Dear me, this has languished a long time.  It would be good to this sorted
 out (at least the spelling part that there's a patch for).

 Looking at the patch, it seems to implement approximately what's sketched
 out in comment:17 and comment:18, except that every candidate causes a
 fetch of the spelling frequency from each of the remote sub-databases, and
 that happens individually, incurring the network round-trip latency each
 time - that seems like it's going to be a performance killer in real-world
 use.

 tizoc - have you been using this patch in production?  If so, how well
 does it work?

 In technical terms, it's not a 1.4.0 blocker (it's ABI-compatible and
 requires a minor protocol version bump), and at this point shortening the
 path to 1.4.0 is an important goal, so adjusting the milestone.

--
Ticket URL: <http://trac.xapian.org/ticket/178#comment:31>
Xapian <http://xapian.org/>
Xapian