-
Notifications
You must be signed in to change notification settings - Fork 58
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
Building DVC Pipelines #765
Comments
Hi @pd-t ! Thanks for the suggestion, more integrations with different orchestrators and execution engines (DVC included) is something that we are currently tracking and planning to work on so its great to hear that there is a need for these features. For DVC specifically, I'll loop in @hogepodge to provide a more concrete timeline and how we're prioritizing orchestrators and execution engines. |
@pd-t quick update. I synced with our team on this and we’re putting it on our roadmap. We've also reached out to the DVC dev team to partner with them to implement this integration. We'll keep you updated on the progress! |
@andycui97 Great news, I am very curious already! |
@pd-t , I've put out the first PR for DVC pipeline support. Right now you can call We're planning to add more options to modularize the stages as you provided in your example so that each stage corresponds to a session or an artifact and have the right dependencies and outputs. Feel free to check the PR here and add comments you may have: #801 |
@andycui97 Great! Unfortunately I was too late for review :( I had a Conference Talk today. But I will have a look on it this week! |
Just noticed this comment but we don't see anything; 😅 did you reach out via one of these options? |
Hi! 👋 Daniel here from team LineaPy. It looks like Doris (Linea's founder) is in touch directly with Dmitry. We plan on following up early next week with more details through one of the links you shared. Thx & look forward to collaborating! 👍 |
@andycui97 I added a pull request for the 'StagePerArtifact' flavour: StagePerArtifact |
@andycui97 With the last pull request, the question now is how to proceed with the module file. Should I try to insert the necessary code sections into the task files with the help of the BasePipelineWriter? |
However, all the requirements described above are met with the PR. So we can also close this ticket and open a new one for this issue. |
I think yes, insert the necessary code into the task files, overriding BasePipelineWriters I also agree, let's open a new Issue for this. |
As DVC user I would like to transform my jupyter notebook into a DVC pipeline using LineaPy.
At the moment it is possible to generate Airflow pipelines as described here. The idea is to add another framework flag for dvc, e.g. framework="DVC".
Now following the Airflow example a set of python source files is generated, i.e. an iris_preprocessed.py
and an iris_model.py file
In addition to this, a DVC yaml file has to be generated, e.g.
Last but not least, a requirements.txt file would finish the DVC pipeline ready for production!
The text was updated successfully, but these errors were encountered: