Member since
03-13-2024
4
Posts
2
Kudos Received
0
Solutions
03-25-2024
06:22 AM
Hi @DianaTorres , Reached out to Impala admin team to resolve the refresh issue in Power BI. Thanks for the support
... View more
03-18-2024
05:11 AM
1 Kudo
Thanks for replying @ChethanYM . For error 1 Do you know how to enable the trace level logging for driver to get more logs? If yes please do share the article. For error 2 to tune the impala admission control pool, do i need to reach Impala admin team.
... View more
03-18-2024
01:33 AM
1 Kudo
Hello @bbreak @ChethanYM, Any suggestions to troubleshoot the refresh issue.
... View more
03-13-2024
06:59 AM
Hello All, We have installed the Cloudera ODBC driver of version 2.6.11 and configured ODBC driver. Making use of impala ODBC as a data source and custom query in Power BI desktop, developed a report and published it into the power bi service. But when i refreshed the dataset to get the updated data in the Power BI report. We are getting below error, can anyone help me to troubleshoot the refresh issue. Error message 1 {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<ccon>ODBC: ERROR [08S01] [Cloudera][ImpalaODBC] (450) Error when calling the Impala Thrift API ExecuteStatement: SSL_read: error code: 0</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"Odbc"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"<ccon>dsn=Impala PROD</ccon>"}},{"code":"Microsoft.Data.Mashup.ValueError.OdbcErrors","detail":{"type":1,"value":"#table({\"SQLState\", \"NativeError\", \"Message\"}, {})"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: New Accounts and Web Changes. Error message 2: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<ccon>ODBC: ERROR [HY000] [Cloudera][ImpalaODBC] (110) Error while executing a query in Impala: [HY000] : Runtime Error: Admission for query exceeded timeout 900000ms in pool root.svcpbigateway. Queued reason: Not enough aggregate memory available in pool root.svcpbigateway with max mem resources 1024.00 GB (configured statically). Needed 232.00 GB but only 68.00 GB was available.\n</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"Odbc"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"<ccon>dsn=Impala PROD</ccon>"}},{"code":"Microsoft.Data.Mashup.ValueError.OdbcErrors","detail":{"type":1,"value":"#table({\"SQLState\", \"NativeError\", \"Message\"}, {})"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: RSA Bill Payments. Thanks in advance!
... View more
Labels: