GitHub user ottobackwards opened a pull request: https://github.com/apache/metron/pull/667
METRON-1061 Add FUZZY_SCORE STELLAR function [Apache Commons Text Similarity](https://commons.apache.org/proper/commons-text/javadocs/api-release/org/apache/commons/text/similarity/FuzzyScore.html) FuzzyScore : "A matching algorithm that is similar to the searching algorithms implemented in editors such as Sublime Text, TextMate, Atom and others. One point is given for every matched character. Subsequent matches yield two bonus points. A higher score indicates a higher similarity." This PR adds FUZZY_SCORE to STELLAR, exposing the Apache Commons FuzzyScore class functionality. This allows for fuzzy matching of strings to queries, and composing statements based on thresholds related to those scores. For example: term = "metron" query = "metron" ```java 16 == FUZZY_SCORE(term,query,'en') ``` +1 for each match and +2 bonus for the 2nd, 3rd, 4th, 5th, and 6th matches. This is related to [METRON-1052](https://issues.apache.org/jira/browse/METRON-1052) ### For all changes: - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? ### For code changes: - [ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed? - [ ] Have you included steps or a guide to how the change may be verified and tested manually? - [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via: ``` mvn -q clean integration-test install && build_utils/verify_licenses.sh ``` - [x] Have you written or updated unit tests and or integration tests to verify your changes? - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`: ``` cd site-book mvn site ``` #### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ottobackwards/metron fuzzy Alternatively you can review and apply these changes as the patch at: https://github.com/apache/metron/pull/667.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #667 ---- commit 34c9ffa97b47005ac10063a43ff1890f51c9a3cf Author: Otto Fowler <ottobackwa...@gmail.com> Date: 2017-07-25T12:31:18Z add FUZZY_SCORE stellar function ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---