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

Explicit workflows #299

Closed
kskyten opened this issue Nov 15, 2017 · 2 comments
Closed

Explicit workflows #299

kskyten opened this issue Nov 15, 2017 · 2 comments
Assignees
Labels
enhancement Enhances DVC

Comments

@kskyten
Copy link

kskyten commented Nov 15, 2017

Defining the workflows implicitly with dvc run is very convenient. However, defining the workflows explicitly adds a possibility for decoupling the workflows from specific repositories. Perhaps it is even possible to have a library of workflow templates. Pachyderm specifies the workflows in a json format, which is probably a good starting point.

@kskyten
Copy link
Author

kskyten commented Nov 15, 2017

On second thought, the json format might not be a good idea. Luigi, which I'm not very familiar with, defines the dependency graph in Python. This is obviously more powerful and it is easier to make workflow templates in code.

@dmpetrov
Copy link
Member

That's funny. Right now @efiop is working on yaml file for dvc run. It is going to be an alternative to implicit dvc run python script.py .... We are going to support both.

Using Python as a format is probably not the best choice for DVC since DVC is language agnostic. Also, we preferred yaml over json because yaml is more human-readable (comments, aliases). While we keep json format for internal machine generated status files.

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

No branches or pull requests

3 participants