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

[Xapian]

#178: No remote backend support for: spelling correction, matchdecider
-----------------------------+-------------------------------
 Reporter:  Richard Boulton  |             Owner:  Olly Betts
     Type:  defect           |            Status:  assigned
 Priority:  normal           |         Milestone:  1.5.0
Component:  Backend-Remote   |           Version:  git master
 Severity:  normal           |        Resolution:
 Keywords:                   |        Blocked By:
 Blocking:                   |  Operating System:  All
-----------------------------+-------------------------------
Changes (by Olly Betts):

 * summary:
     No remote backend support for: spelling correction, matchdecider,
     metadata_keys_begin()
     => No remote backend support for: spelling correction, matchdecider


Old description:

> The remote database was briefly feature complete, but it's fallen behind
> again -
> it doesn't support spelling correction or matchdeciders.
>
> Metadata is partly supported, but metadata_keys_begin() isn't.
>
> We should add these in to it at some point.

New description:

 The remote database was briefly feature complete, but it's fallen behind
 again -
 it doesn't support spelling correction (adding and removing spellings at
 index time is supported though) or matchdeciders.

 We should ideally add these in to it at some point.

--
Comment:

 `metadata_keys_begin()` was actually implemented a long time ago, back in
 2010 in [eacacefcc5d29c95292a7b1a26cd8fa5a904748a] which debuted in
 1.2.20.  It's tested by testcase `metadata5` which runs and passes for
 remote backends.
-- 
Ticket URL: <https://trac.xapian.org/ticket/178#comment:35>
Xapian <https://xapian.org/>
Xapian