Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Double-metaphone match not working #290

Open
wooldridge opened this issue Feb 14, 2019 · 0 comments
Open

Double-metaphone match not working #290

wooldridge opened this issue Feb 14, 2019 · 0 comments

Comments

@wooldridge
Copy link

The double-metaphone match feature is not working for me. I'm attaching a QConsole workspace that works with the minimal-smart-mastering-content database. It does the following:

  • Loads 3 sample docs
  • Creates an element range index for the property being matched on ("prop")
  • Saves match options that have a double-metaphone option
  • Runs a match using the options and sample documents

In the match results, I get the expected exact match (/doc1.json and /doc3.json) but not the expected double-metaphone match (/doc1.json and /doc2.json). I'd expect "pair" to match "pear" via double-metaphone.

Double-Metaphone-Workspace.xml.zip

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant