How to resolve build failure due to timeout with CData JDBC Driver for REST [Linux]
This article provides guidance for extending a timeout value when a build fails with the following error during importing data from a REST data source using the CData JDBC Driver for REST. 7000 | Table query error Verify the data source and table are available for query. Try building sample data on a duplicate cube. Build failed: base table "table_name" was not completed as expected. Failed to read row: 0, Connector (Timeout.).
Step-by-Step Guide:
The build error due to a timeout of the REST connector occurs when the executed REST API does not return any response within the configured timeout. It can be set in the connection string. If the timeout option is not set in the connection string, the default value is 60 seconds. You can set the default timeout value in the created Generic JDBC connector of the CData JDBC Driver for REST with the following steps.
- Log in to Sisense with an Admin role user
- Open Configuration Manager, click Admin > Server & Hardware > System Management > Configuration
- In the Configuration Manager, click the Manage Connectors link at the bottom of the page
- Select your Generic JDBC REST connector in the left pane
- Expand the Advanced Configuration in the right pane
- Add the timeout parameter in the Connection string parameters in the right pane :
Example:timeout=300;
- Click the Update button
If you don’t want to extend the default timeout value, you can add the timeout option in the connection string of each connection.
Note:
To set the timeout value, please use a third-party tool to execute the request and set a sufficient time based on how long it takes to perform the REST request.
Conclusion:
By setting the timeout value to a sufficient amount of time for getting a result from the configured REST request, it prevents the build failure due to the timeout error.
References/Related Content
https://cdn.cdata.com/help/DWK/jdbc/RSBREST_p_Timeout.htm
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
