DirectQuery Impala Connector for Power BI Report Server
According to the documentation, Scheduled Refresh and DirectQuery are not supported for the Impala connector in Power BI Report Server? https://docs.microsoft.com/en-us/power-bi/report-server/data-sources However, in the Power BI Desktop for Report Server, DirectQuery is one of the options for connection. Can anyone clarify if DirectQuery is really supported or not for the Impala Connector in Power BI Report Server? Thanks!Incremental Refresh Unstable (Impala & Kerberos)
Hi all, I'm pretty new to PBI and keen to actually get using the full power of PowerBI but at the moment I'm stuck in data access limbo. We are using Kerberos authentication to connect to an Impala database. The initial connection is fine (ie. we can get data and set up incremental refreshes) and the incremental refreshes will generally perform ok for a few days and then fail, then maybe start again, fail (repeat) before eventually flaming out and disabling themselves. I have been on endless calls with our PBI Support Team who say that it's not a PBI error. They blame the database team who say it's not their problem...it's a network issue, and the network team blame PBI Team.....and around it goes 😞 I know that this will be virtually impossible to diagnose and fix via a forum but would be keen to hear if Impala + Kerberos has worked for anybody to at least give me confidence it can be achieved 🙂 Example of error message: "Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support. {"error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","pbi.error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<ccon>[Microsoft][ThriftExtension] (3) Error occurred while contacting server: SSL_read: error code: 0. The connection has been configured to use a SASL mechanism for authentication. This error might be due to the server is not using SASL for authentication.</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"Impala"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"<servername.com</ccon>"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessUnauthorized"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"<ccon>[{\"kind\":\"Impala\",\"path\":\"servername.com\"}]</ccon>"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessUnauthorized"}}],"exceptionCulprit":1}}}"
