Inaccurate results are returned when the CONTAINS operator is used in the table viewer filter for a large database table. Refreshing the table might then result in the filter being completely removed.

The workaround for this problem is to use the LIKE operator instead of the CONTAINS operator.

Also, when you apply the filter to an Apache Hadoop table, the following pop-up error message can appear:

A possible circumvention is to set the environment variable SAS_HADOOP_ENABLE_INTERRUPT to NO. This variable is specified in the sasv9_usermods.cfg configuration file that is specific to the application server that is being used by SAS Studio. Submit this command:

This environment variable can also be set in an OPTIONS statement within the SAS^® program or in the autoexec file, as follows:

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Viya on Linux: An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at

Viya on Windows: An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Windows Deployment Guide at

An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Windows Deployment Guide at

An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at

A fix for this issue for SAS Studio 3.8 is available at:

A fix for this issue for SAS Studio 3.71 is available at:

A fix for this issue for SAS Studio 3.7 is available at: