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

[CLOUDEXEC-766] Add callback function. #203

Merged
merged 62 commits into from
Mar 28, 2023
Merged

[CLOUDEXEC-766] Add callback function. #203

merged 62 commits into from
Mar 28, 2023

Conversation

dichenqiandbt
Copy link
Contributor

What is this PR?

This is a:

  • documentation update
  • bug fix with no breaking changes
  • new functionality
  • a breaking change

All pull requests from community contributors should target the main branch (default).

Description & motivation

Added callback function in celery task, it will be triggered once state is updated.

Checklist

  • I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)
    • BigQuery
    • Postgres
    • Redshift
    • Snowflake
    • Databricks
    • Spark
  • I have updated the README.md (if applicable)
  • I have added tests & descriptions to my models
  • I have added an entry to CHANGELOG.md

racheldaniel and others added 30 commits December 2, 2022 09:20
* Support partial parsing

* Updates todo
* possible way of intergrating all of the dbt commands

* somewhat working version of a generalized framework

* working version of run, a lot of refactor and better core interface needed

* using some new interface

* remove unused function

* using state for run task

* some clean up

* Resolves merge conflicts (#145)

* Core integration updates (#148)

* Updates state_id usage

* Moves task logic to StateController

* removes hardcoded command

* Initiates logmanager in async function

* Removes old async logic and reinstates python logger for dbt-server

Co-authored-by: Rachel <[email protected]>
Co-authored-by: Rachel Daniel <[email protected]>
…irements.txt to resolve error handling issue with underlying FastAPI dependency (#149)

* Upgrade FastAPI version in requirements.txt and add httpx to dev-requirements.txt to resolve error handling issue with underlying FastAPI dependency

* Add changelog entry
* possible way of intergrating all of the dbt commands

* somewhat working version of a generalized framework

* working version of run, a lot of refactor and better core interface needed

* using some new interface

* remove unused function

* using state for run task

* some clean up

* Core integration updates (#148)

* Updates state_id usage

* Moves task logic to StateController

* removes hardcoded command

* Removes old async logic and reinstates python logger for dbt-server

* Beginning logic to accept a project path

* Adds project_path storing and cacheing

* Removes prints and fixes caching issue

* removes unused task functions

* adds changie entry

* removes dup code from rebase error

* removes dup code from rebase error

* removes dup code from rebase error

* Adds tests for dbt_entry and preliminary state tests

* Removes unused file

* Copies minimal project to tempdir to avoid writing files

Co-authored-by: Chenyu Li <[email protected]>
Co-authored-by: Chenyu Li <[email protected]>
* Updates async endpoint to use set_profile_name function

* Adds checkfirst flag to avoid table exists error

* Fixes profile name and potential fix for sqlalchemy error

* Adds profile back to command args

* Fixes whitespace

* Adds status endpoint
* Adds sync endpoint and fixes linting

* Adds test for sync dbt entry endpoint

* Fixes formatting

* Adds changie entry
* Add the requests library to the requirements

* Replace each specific task update method with a generic method so that it can be called cleanly upstream

* Update this class to use camel casing

* Add new update task status method that sets the task status in the local DB as well as calling the callback if there is one

* Accept a callback url and pass it to the async command method

* Call the new update task status method where the crud methods were previously called

* Move requests from the dev requirements to requirements

* Return the state ID in addition to the other task fields in the async response

* Remove commented out code

* Specify to retry post requests since it isn't enabled by default

* Update dbt_server/views.py

Co-authored-by: Rachel <[email protected]>

* Rename DBTCommandArgs to DbtCommandArgs

* Add a change log entry

---------

Co-authored-by: Rachel <[email protected]>
* Updates db path to working dir instead of app root

* Solidifies locations that the dbt-server writes to

* Changes back to app root after dbt command run

* Fixes comment
…creating the async task. If not present, create a task ID and use it (#168)
* Fix tests.

* Fix wrong package

* Remove adaptor requirements and skip tests without dependency.

* Fix wrong package name
* Resolves merge conflicts

* Cherry-pick gone awry

* spaces

* Allows images to build on PR
* Removes conditional on test, tailors to branch

* Adds changie entry

* Comments out unused matrix
dichenqiandbt and others added 22 commits February 27, 2023 14:46
* Add smoke test and check in test dbt project jaffle shop.

* nits

* nits

* Add changie

* Update smoke test.

* Start dbt-server inside smoke test.

* Fix format.
@cla-bot cla-bot bot added the cla:yes label Mar 28, 2023
@github-actions
Copy link

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

@@ -97,7 +111,8 @@ def _invoke(task: Any, command: List[str], callback_url: Optional[str] = None):
task_id = task.request.id
_insert_log_path(command, task_id)
logger.info(f"Running dbt task ({task_id}) with {command}")
# TODO: Send callback to infer task start.
if callback_url:
_send_state_callback(callback_url, task_id, STARTED)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So at this point the task would technically show PENDING if we called for the status, right? I see how this gives the caller more accurate information, I'm just curious as to your thinking around sending this here rather than doing a _get_task_status() after we call t.start(). Is there a chance we tell a client the task has started and then it actually fails to start?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually it shows STARTED not PENDING. PENDING = task is created buy still wait for worker process to pickup. STARTED = task has been picked up by worker. STARTED is automatically set by celery as I passed
track_started=True.

But you gave me a very good hint! I should try catch in callback helper to make sure it doesn't halt worker.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh cool, thanks so much!

Copy link
Contributor

@racheldaniel racheldaniel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one clarifying question!

@dichenqiandbt dichenqiandbt merged commit 3f96cdd into main Mar 28, 2023
@dichenqiandbt dichenqiandbt deleted the dichen/dev_1 branch March 28, 2023 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants