Change in the handling of Memory model queries using $like comparison operator

Change in the handling of Memory model queries using $like comparison operator

Models using the Memory connector return an empty result set when attempting to perform a query that uses the $like operator. For example:

This behavior has been deprecated since the API Builder Standalone - Eden release. 

Beginning with the Eden release, queries on models that use the Memory connector will support the $like comparison operator.

This will be the default behavior in all new services. 

Why are we deprecating this feature

Previously, queries on Memory models that attempted to use the $like comparison operator would return an empty result set. This could result in logic errors in your flows or APIs and is not the expected behavior of the feature. It should return a result set that matches the query passed to it.

How does this impact my service

This is now the default behavior for all new services. Any existing services will continue to work as they previously did, though it is strongly recommended you enable the new behavior on existing services.

The changed behavior only impacts services that query models which are using the Memory connector and those queries are using the $like operator.

Upgrading existing services

Updates contain important changes to improve the performance, stability, and security of your services. Installing them ensures that your software continues to run safely and efficiently.

It is strongly recommended you upgrade API Builder to the latest version as well any data connectors you may have in your stack. This feature requires a minimum of:

  • API Builder Standalone - Eden

After upgrading, the enableMemoryConnectorLike feature will not be active until you enable it. To enable it, add the following setting to your default.js file.

flags: {
    enableMemoryConnectorLike: true
}

More default.js configuration file information can be found here: Project Configuration

Related Links