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

[CT-70] [Feature] Public API returns task or task.manifest #4593

Closed
1 task done
ismailsimsek opened this issue Jan 19, 2022 · 1 comment
Closed
1 task done

[CT-70] [Feature] Public API returns task or task.manifest #4593

ismailsimsek opened this issue Jan 19, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@ismailsimsek
Copy link

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

Is there public api to return task or task.manifest. which is useful to integrate db to external applications like airflow

Currently handle_and_check is not returning task, if it was that would work too.

having manifest.nodes makes it possible to create Airflow dag with granular tasks( a task per model) with correct dependencies.

example:

  1. run dbt parse
  2. retrieve manifest
  3. create airflow DAG tasks per manifest.node with correct dependencies (using manifest.node.depends_on)

this makes it possible to run some custom checks before running model
for-example running tests on all source dependencies and then running the model.

related #2013

Describe alternatives you've considered

No response

Who will this benefit?

Anyone using dbt with Airflow

Are you interested in contributing this feature?

No response

Anything else?

No response

@ismailsimsek ismailsimsek added enhancement New feature or request triage labels Jan 19, 2022
@github-actions github-actions bot changed the title [Feature] Public API returns task or task.manifest [CT-70] [Feature] Public API returns task or task.manifest Jan 19, 2022
@gshank gshank removed the triage label Jan 20, 2022
@gshank
Copy link
Contributor

gshank commented Jan 20, 2022

The dbt 'parse' command with the '--write-manifest' option will write out the manifest.json file, which is the official interface for that information. From the manifest.json you could get the node and depends_on information.

Since we do provide an official source of this information, I'm going to close this ticket, but if you feel that this doesn't address your needs, please update with additional information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants