KB316725: Users are unable to filter tables belonging to a specified schema in the MicroStrategy Warehouse Catalog while using the MicroStrategy Hive ODBC driver

SYMPTOM
In Strategy Secure Enterprise 10.4 and later, when trying to view the warehouse catalog while connecting to a Hive instance that uses the Strategy Hive ODBC Driver, users might see various tables belonging to different schemas being displayed. This may lead to a degradation in performance or cause the Warehouse Catalog to hang.
 
CAUSE
This behavior is expected with the Strategy Warehouse Catalog as it cannot filter based on a specific schema. 
 
ACTION

• Create a new DSN from the  ODBC administrator and use the Strategy ODBC Driver for Hive Wire Protocol instead of using the 'Strategy Hive ODBC Driver'. The Strategy Hive driver is a new driver that is available in the product starting with Strategy version 10.4 as shown below. 
  
  

• After creating a DSN with the Strategy ODBC Driver for Hive Wire Protocol, navigate to the Advanced settings and enable the 'Use current schema for catalog functions' check box from the advanced tab. 
  
  

• On Linux operating systems, edit the odbc.ini file and create a DSN to hive using the Strategy ODBC Driver for Apache Hive Wire Protocol (Refer to the odbc.ini.example file). Set the following  parameter: UseCurrentSchema=1
   
• While using Strategy Desktop or Strategy Web, check the 'Edit connection string' check box and update the connection string to the following after replacing the values for servername,portname and database:
   
  

  
  DRIVER={Strategy ODBC Driver for Apache Hive Wire Protocol Desktop};HostName=servername;PortNumber=portname;Database=database;WireProtocolVersion=2;UseNativeCatalogFunctions=1;UseCurrentSchema=1;

  
  
  
  
  

Note: Even though all the namespaces show up, only tables the database specified in the data source creation (wh2 in the following example) will be displayed: