Hi all, we are setting up dbt-elementary for the first time and on running edr report, the generated report is coming back as empty whereas elementary_test_results has data. The edr logs have the following error: ERROR � Could not generate the report - Error: Failed to run dbt command. {"info": {"name": "RunningOperationCaughtError", "code": "Q001", "msg": "Encountered an error while running operation: Database Error\n Database Error\n \n [TEMP_VIEW_NAME_TOO_MANY_NAME_PARTS] CREATE TEMPORARY VIEW or the corresponding Dataset APIs only accept single-part view names, but got: We are using Databricks and thats the reason it complains about the "too many parts", looks like its failing to create the temp view as hive_metastore and the schema is getting appended to the CREATE command. Has anyone come across this error? If so, do let me know how you troubleshooted it. Thanks in advance

Hi Sonam, we have got the same issue on databricks, notice that our elementary report has been working for nearly a month, but just broke yesterday. We are looking for a solution as well. 🥲 thanks for raising this issue, hopefully someone can help. 🙇 We are using 0.17.0, tried with 0.18.1 but no luck.

Hey @Sonam K @Jasper Ma! Looking into it. What dbt package are you using? @Jasper Ma, did the report break with an Elementary update or all of a sudden?

@Noya Offer, thanks for your help. I’m using

dbt=1.9.4

, and the registered adapter is

databricks=1.10.0

. I started breaking since yesterday without any elementary update. We are still using dbt elementary version

0.17.0

Did you happen to update dbt recently?

nope, we have been using that dbt version for months.

Hey @Noya Offer, we are using- dbt-core:1.9.3 elementary-data/elementary: 0.18.2 databricks: 1.9.7 Referring back to this thread, https://github.com/elementary-data/elementary/issues/1048 it seemed that the issue was fixed for spark and Databricks but looks like its not Could you please guide us on how to proceed as we are completely blocked atm.

@Sonam K is the CLI version also 0.18.1 ? 🙂

yes, CLI version is 0.18.1

We've got the same issue. Using 0.18.1 for both versions, dbt-databricks=1.10.0. Did not have the issue before upgrading dbt-databricks.

Hi @Noya Offer, do you have any updates for us? Can you give some pointers on how to debug this? Or which macro is getting called on running "edr report" so that we can look at overriding specific macro?

I can give an update from our POV. edr report fails in this step: INFOelementary.clients.dbt.command line dbt runnerRunning dbt command --log-format json run-operation elementary.log_macro_results --args {"macro_name": "elementary_cli.get_test_results", "macro_args": {"days_back": 7, "invocations_per_test": 720, "disable_passed_test_metrics": false}} --project-dir /local_disk0/.ephemeral_nfs/envs/pythonEnv-41445283-eae7-413a-a273-00752d71b03d/lib/python3.10/site-packages/elementary/monitor/dbt_project --profiles-dir /Workspace/Live_dbt {"data": {"exc": "Database Error\n Database Error\n \n [TEMP_VIEW_NAME_TOO_MANY_NAME_PARTS] CREATE TEMPORARY VIEW or the corresponding Dataset APIs only accept single-part view names, but got:

dae_nexus_prod

.

elementary

.

ordered_test_resultsnone

. I re-ran it with %pip install dbt-databricks==1.9.7 %pip install elementary-data==0.17.0 and did not get an error.

I tried the same versions as you, where it worked for you but didnt work for me unfortunately. Still getting the same error.

I got the same error on creating the same temporary view. We have been using the same package versions(1.9.7, 0.17.0) for months and started getting this error two days ago.🥲

Thank you @Jasper Ma @Sonam K @Christian Demant ! The failed edr logs are very helpful to debug this. Out team will look into this issue on Monday 🙏🏼

I have opened a bug to track this issue -> https://github.com/elementary-data/elementary/issues/1895 fyi - @Noya Offer @Jasper Ma @Christian Demant

I think I’ve found the fix for this. create_temp_table.sql needs an override for the databricks adapter similar to how snowflake has been handled. I have added comments to the ticket.

Thanks, @Dave Beastall! Let me take a deeper look. @Sonam K Can you please share the edr logs again? Sorry to ask this, but the file is not found now.

Hi @Noya Offer - sharing the edr logs again.

Hi @Noya Offer, no I didn’t.

Hi @Noya Offer - any findings or updates on fix so far?

Support is packed today but our CTO is looking into it. I'll let you know as soon as we have a better understanding of this!

Absolutely, @Itamar Hartstein is on it. Appreciate your cooperation and help on this!

Hi @Noya Offer, thanks for supporting. Has there been any further update on this one since last Wednesday?

Hi @Noya Offer - wondering if you have any updates for the issue reported above? We do have a workaround for now, but would be good to have it working in the latest version as well. Let us know. Thanks in advance

Hi @Noya Offer, wondering if the the root cause of this issue has been found or any workaround for this? thanks!

Hey @Jasper Ma @Sonam K, this is taking a bit longer than we thought but we've prioritized this and actively working on it. Our next CLI release that's planned for this week is waiting for this fix, so it will be released as soon as we implement the solution 🙏

Hi @Noya Offer, I can see that the latest version of dbt elementary is now

0.18.3

, is this issue fixed by this release?

Hey @Jasper Ma ! Absolutely 🚀 Was away for a couple of days so didn't update yet. Sharing the full release message soon 🙌 Thank you for your cooperation and patience!

Thank you @Noya Offer, looking forward to try out the new release.