cancel
Showing results for 
Search instead for 
Did you mean: 
nataliia_kh
Sisense Team Member
Sisense Team Member

Mongo issue and their possible solutions 

The query translated from SQL to MQL is adding additional unnecessary parameter {"$not": {"$type": 2}} randomly. 

This leads to the following consequences: 

  • index is not included in the execution plan  
  • full table scan at the MongoDB end is executed 
  • The initialization step can take around 50% of the total time of the EC build 
  • Cube builds take more time overall 

Resolution: 

When connecting to MongoDB add the ‘EnableMixedTypeFilter=0;’ parameter in the ‘Additional parameters’ section

Screenshot 2025-01-31 at 12.20.45 PM.png

[ALT Text: A blurred screenshot of a user interface displaying settings related to sampling. Key fields include "Sampling Count" set to 100, "Sampling Interval" set to 1, and an additional parameters section highlighting "EnableMixedTypeFilter" with emphasis on its label. There are buttons labeled "Save" and "Share" at the bottom.]

There are specific field(s) in the collection in MongoDB, which are missing from the table after you build the cube in Sisense. 

The method used to identify the fields, which became columns is sampling. By default, it scans forward (100 first ro So, in case specific field(s) were added later on and are not present in the first 100 rows, they will be excluded from the  

Resolution: 

When connecting to MongoDB adjust the ‘Sampling Method’ parameter to ‘Backwards’ to scan collection from the most recently added data. 

 

Screenshot 2025-01-31 at 12.22.38 PM.png

[ALT text: An interface displaying two dropdown options labeled "Sampling Method" and "Sampling Count." The "Sampling Method" option is highlighted in red, showing "Backwards" selected. The "Sampling Count" is set to 100, indicated by the input field below.]

When connecting to MongoDB, you need to use a trust store file along with self-signed certificates. 

Please consider that this should be used only for dev as a short-term solution (when you run some tests, etc). Resolution: 

  1. Once you choose the ‘Enable SSL’ option for MongoDB connector, you may see 2 new fields appearing: Trust Store a Trust Store Password

Screenshot 2025-01-31 at 1.37.12 PM.png

[ALT text: A screenshot of a user interface showing options for enabling SSL, with fields for "Trust Store" and "Trust Store Password" presented. The fields are empty, indicating that no information has been entered.]

A trust store is a file that contains certificates used to verify the identity of the server you're connecting to. For a self-signed certificate, you'll need to create a trust store that includes this cert 

  1. Firstly you need to convert your certificate file to a .pem extension. Then create a trust store and import your certi (you may use the 'keytool' command-line utility, which is part of the Java Development Kit (JDK) or any other way you usually use to create a trust store). 
  2. After you have your certificate ready you need to fill out SSL f 

Trust Store - Enter the path to your trust store file (place it in some folder in the Admin tab - File management section and enter the path to that file. Path to the File management root folder is '/opt/sisense/storage 

For example, if you place the certificate in the ‘data’ folder, the path to it will be '/opt/sisense/storage/data

 

Screenshot 2025-01-31 at 1.40.16 PM.png

[ALT text: Blurred screenshot of a user interface for file management, featuring a search bar, sections for user files and folders, and a message that says "It feels lonely here..." accompanied by a sad face icon. The interface also includes options for settings and configuration.]

Trust Store Password - Enter the password you specified when creating the trust store password

Rate this article:
Version history
Last update:
‎01-31-2025 12:08 PM
Updated by:
Contributors