Open rafaelmarinm opened 8 months ago
@rafaelmarinm thanks for opening this issue. We have seen similar issues of customers running into the same manifest error when deploying to either Fivetran or dbt Cloud. Since this runs fine locally, there must be something going on when trying to orchestrate the models and the manifest somehow gets in the way.
@Jstein77 do you have any thoughts as to what this manifest error is? It's interesting that this runs normally in a local environment but not when deploying for orchestration?
Hey @rafaelmarinm sorry for the delay! I was on vacation for the last 2 weeks. I tried to repro this issue using the same dbt version in a clean venv and wasn't able to - the fivetran package installed successfully and dbt compile ran as well. Are you still blocked here?
Hi Jordan! Yes still blocked. If you can we can have a Zoom meeting to go over all the details.
On Wed, Nov 15, 2023 at 1:36 PM Jordan @.***> wrote:
Hey @rafaelmarinm https://github.com/rafaelmarinm sorry for the delay! I was on vacation for the last 2 weeks. I tried to repro this issue using the same dbt version in a clean venv and wasn't able to - the fivetran package installed successfully and dbt compile ran as well. Are you still blocked here?
— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_ad_reporting/issues/106#issuecomment-1813147063, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7NVIMGQQUQXOZXZQRAALFTYEUKVNAVCNFSM6AAAAAA6TJXPDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGE2DOMBWGM . You are receiving this because you were mentioned.Message ID: @.***>
Hi @rafaelmarinm one quick thought, do you have a package-lock.yml
in your project? If so, can you try and delete that file, then rerun dbt clean && dbt deps && dbt run
to see if that resolves the issue.
I mainly ask, because @fivetran-catfritz on my team noticed the ad_reporting_metrics
file that is causing the issue has since been deprecated following one of the latest releases. I think the old version of ad reporting may still be in use due to the package-lock.yml and we just need to reset it.
Let me know!
@rafaelmarinm Feel free to book some time to go over this issue! https://calendly.com/jordan-stein-1
Hi @rafaelmarinm I am curious if my above suggestion worked for you? Otherwise, were you able to meet with @Jstein77 to investigate further?
I will continue to leave this ticket open in case others have more to share in the thread. However, I will mark the ticket as wontfix
since it seems there may not be any updates that need to be applied to the Ad Reporting package.
Please let me know if anyone believes there should be an update to the package. Thanks!
Hi @fivetran-joemarkiewicz, I ran into a similar issue. I'm using dbt version 1.7.3 and tried to run the ad_reporting project on Fivetran. I'm seeing the following error
The node semantic_model.ad_reporting.ad_report not found
It works without any issue if ran locally. Would you be able to help to identify the issue?
As identified within Issue #108, the root cause of this issue seems to be caused by Fivetran transformations not taking into account the semantic_manifest.json
. This is not something that will result in an update within the dbt package itself. Instead, if any others come across this issue, please open a Fivetran Support Ticket.
Thank you!
Is there an existing issue for this?
Describe the issue
I am trying to install the ad reporting model package in fivetran and I have not been able to get it to run. It runs fine in my local environment, but once I try to run it in fivetran I get the same error.
Details:
dbt configuration passed all checks
package: fivetran/ad_reporting version: 1.7.0
dbt version: 1.6.6
Error: The following dbt command:
Relevant error log or model output
No response
Expected behavior
Deploy ad reporting model
dbt Project configurations
Package versions
package: fivetran/ad_reporting version: 1.7.0
What database are you using dbt with?
snowflake
dbt Version
1.6.6
Additional Context
No response
Are you willing to open a PR to help address this issue?