SAP HANA Developer Guide - Get a Free Blog

FUZZY(0.8,
'termMappingTable=termmappings,termMappingListId=01,textSearch=compare'))
ORDER BY score DESC, id;
SCORE ID COMPANYNAME
1.0 2 SAP Aktiengesellschaft
0.9 1 SAP AG
SELECT TO_DECIMAL(SCORE(),3,2) AS score, * FROM companies
WHERE CONTAINS(companyname, 'sap ag',
FUZZY(0.8,'termMappingTable=TERMMAPPINGS,termMappingListId=01,textSearch=co
mpare'))
ORDER BY score DESC, id;
SCORE ID COMPANYNAME
1.0 1 SAP AG
0.9 2 SAP Aktiengesellschaft
To activate language-specific term mappings, you must provide the language parameter:
SELECT TO_DECIMAL(SCORE(),3,2) AS score, * FROM companies
WHERE CONTAINS(companyname, 'sap ag',
FUZZY(0.8,'termMappingTable=TERMMAPPINGS,termMappingListId=01,textSearch=co
mpare'), language('de'))
ORDER BY score DESC, id;
Note: In this case, all term mappings where language_code is set to 'de' or empty will be used. Any term
mappings with other language codes will be ignored.
Fuzzy Search on DATE Columns
A fuzzy search on DATE columns supports two types of error:
● Date-specific typos
● Dates lying within a user-defined maximum distance
Score Calculation for Typos
Instead of using Levenshtein distance or other string-compare algorithms, the following date-specific typos and
errors are defined as similar:
1. One wrong digit at any position (for example, 2011-08-15 instead of 2011-08-25). This type of error gets a
score of 0.90.
2. Two digits interchanged within one component (day, month, or year) (for example, 2001-01-12, 2010-10-12, or
2010-01-21 instead of 2010-01-12). This type of error gets a score of 0.85.
3. Month and day interchanged (US versus European date format) (for example, 2010-10-12 instead of
298
2010-12-10). This type of error gets a score of 0.80.
P U B L I C
© 2012 SAP AG. All rights reserved.
SAP HANA Developer Guide
Enabling Search