On Jan 13, 2016, at 4:16 PM, Brendan Duddridge <[email protected]<mailto:[email protected]>> wrote:
Is using * for a prefixed query considered "fancy"? Yes, anything with metacharacters or reserved words is “fancy” in this context. The implementation for ForestDB just looks up words. The one special thing it does is ‘stemming<https://en.wikipedia.org/wiki/Stemming>’, which means that it tries to remove English suffixes before indexing and querying — that way “big” and “bigger” will match, and “walk” and “walking”. (For both SQLite3 and ForestDB we’re using the “Snowball<http://snowballstem.org>” stemmer, with sources taken from the sqlite3-unicodesn<https://github.com/illarionov/sqlite3-unicodesn> library. It supports about a dozen languages.) I could add prefix matching, but not for 1.2. Please file an issue. Mostly it seems pretty easy to implement, except for possible weird interactions with stemming. (Hm, might be a fun Summer Of Code project for someone…) Does this mean that I'll have to emit "x, xb, xbo, and xbox" in my map block in order to facilitate prefixed searches? Ugh, I reluctantly say “yes” because I can’t think of any better workaround :/ Although really all you need is “x xb xbo xbox”, since commas and noise-words like “and” are ignored.* —Jens * Actually that’s another special thing. Two special things! Amongst our special things are such diverse elements as… -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/C67BD2E1-48E6-43B9-8674-32932FCC74AB%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
