Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISSUE_FIELD_HISTORY #128

Open
2 of 4 tasks
maliro opened this issue May 22, 2024 · 2 comments
Open
2 of 4 tasks

ISSUE_FIELD_HISTORY #128

maliro opened this issue May 22, 2024 · 2 comments
Labels
type:wontfix This will not be worked on

Comments

@maliro
Copy link

maliro commented May 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Describe the issue

We upgrade the Jira fivetran package to 017 in dbt.
ISSUE_FIELD_HISTORY query fails after running over than 2 hours on snowflake warehouse : size XXL.
Could we please set a meeting? I will appreciate your advice.

Relevant error log or model output

dbt command failed13:57:48 48 of 59 ERROR creating sql incremental model dwh_jira_cloud_cx.jira__daily_issue_field_history  [ERROR in 7201.90s]

13:57:48  Completed with 1 error and 0 warnings:
13:57:48  
13:57:48  Database Error in model jira__daily_issue_field_history (models/jira__daily_issue_field_history.sql)
13:57:48    000630 (57014): Statement reached its statement or warehouse timeout of 7,200 second(s) and was canceled.
13:57:48    compiled Code at target/run/jira/models/jira__daily_issue_field_history.sql

Expected behavior

I expect that this query will finish to run. size warehouse xxl is very big there is no reason why it is failing
version 15 of Jira package did succeed.

dbt Project configurations

packages:

  • package: fivetran/jira
    version: 0.17.0

Package versions

version: 0.17.0

What database are you using dbt with?

snowflake

dbt Version

dbt v1.5.0-latest

Additional Context

/

Are you willing to open a PR to help address this issue?

  • Yes.
  • Yes, but I will need assistance and will schedule time during our office hours for guidance
  • No.
@fivetran-reneeli
Copy link
Contributor

Hi @maliro thanks for opening this. My thinking is this may be caused by recent updates we made to the incremental logic in the models. I think it would be helpful to debug this live; here is a booking link! Looking forward to speaking soon!

@fivetran-reneeli fivetran-reneeli added the type:wontfix This will not be worked on label Jun 6, 2024
@fivetran-reneeli
Copy link
Contributor

Will mark as won't fix for the time being until there is further customer interest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants