Skip to Content

CAP and HANA fuzzy search

I noticed in the release notes for 2020 that for $search the HANA fuzzy searched was replaced by the usage of LIKE.

Does anybody know what was the motivation for this?

I always thought it was cool to utilize a search engine which is capable of also finding slightly misspelled stuff.

Add a comment
10|10000 characters needed characters exceeded

  • My guess is that this is in order to align with "being opinionated" about Higher-level concepts and APIs ( To me, this reads like that no platform (in this case DB platform) specific features are used to make public APIs/public visible behavior.

    No other DBMS supports fuzzy search (and it comes with limitations concerning what column types it works on). So maybe the CAP developers thought it was a good idea to do what every other DBMS does: (ab)use the LIKE operator as a kind of largest common denominator.

    They've also done that with the implementation of temporal tables on HANA. While HANA provides specific table types for that purpose, the CAP implementation rolls its very own temporal table design.
    If my thinking is correct here, I'd consider it a mistake to not allow HANA to leverage its features. SAP made the mistake of supporting several DB platforms by using only the features that the DBs have in common before - not sure why this lesson doesn't seem to stick.

Related questions

0 Answers

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.