Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Error connecting to Databricks 7.3 LTS (includes Apache Spark 3.0.1) using Spark connector

Refreshing Dataset is failing with this error. Also connecting to the Data Source using the Spark connector. It is intermittent.

 

Processing error: ODBC: ERROR [42S02] [Microsoft][SQLEngine] (31740)

Table or view not found: SPARK.<table/View name>
Cluster URI: WABI-US-EAST-A-PRIMARY-redirect.analysis.windows.net
Activity ID: 30b9464f-c5eb-4803-87ac-b2c0505f5cf8
Request ID: 66497276-ff29-a034-cbc5-ad858001a110
Time: 2021-07-18 21:06:42Z

 

The view exists.... It is intermittent ... wondering if there is a timeout when retrieving object that can be set?

 

Any help or suggestions will be greatly appreciated.

3 Replies

  • v-janeyg-msft's avatar
    v-janeyg-msft
    Icon for Community Support rankCommunity Support

    Hello, Anonymous 

     

    Sorry, we can’t reproduce your scene. Has the desktop version of the report published and the gateway used for refreshing been upgraded to the latest version? What connection mode is used?

    Reference:

    Power BI - Azure Databricks - SQL Analytics | Microsoft Docs

     

    Did I answer your question ? Please mark my reply as solution. Thank you very much.
    If not, please feel free to ask me.

     

    Best Regards

    Janey Guo

  • Anonymous's avatar
    Anonymous
    Not applicable

    v-janeyg-msft 

     

    Hello,

    We do not have a gateway. The issue with Refresh is happening in both the Deskop and the Power BI Service. I'm on the June 2021 version of the Desktop. Import Mode connection is used.

     

    I worked fine with version 6.x of Databricks, we experience this issue very often now after upgrading to version 7.3 and it is happening with both the Azure Databricks and Spark connector.

     

    Thanks for looking into it,

    Maryno

    • v-janeyg-msft's avatar
      v-janeyg-msft
      Icon for Community Support rankCommunity Support

      Anonymous 

       

      According to your description, this may be the problem of version incompatibility, We may not be able to provide effective support here. We suggest you use the older version.

       

      Did I answer your question ? Please mark my reply as solution. Thank you very much.
      If not, please feel free to ask me.

       

      Best Regards

      Janey Guo