-
Notifications
You must be signed in to change notification settings - Fork 704
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
[Plugin] Hamilton #2627
Comments
Thank you for opening your first issue here! 🛠 |
Related feature idea - stitchfix/hamilton#139 |
From @samhita-alla some examples to think look at:
Reference documentation - https://docs.flyte.org/projects/cookbook/en/latest/auto/core/extend_flyte/custom_task_plugin.html |
Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏 |
Oops. Definitely forgot about this one. Will figure out it's priority next sprint. |
So circling back to this. We're looking to schedule this for sometime in November/December. |
Sorry -- still working on this one. |
I'll get to this eventually... |
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. |
Yeah I think it makes sense to close for now. Haven't had the pull to bump it up in priority. |
What: https://github.com/stitchfix/hamilton defines a way to model a micro-workflow. Flyte models a macro view. So idea (I think) would be to run a Hamilton DAG within a flyte task more easily than it would be now.
i.e. replace this driver code that would be put into a flyte task:
See https://github.com/outerbounds/hamilton-metaflow for an example of Hamilton + metaflow -- hamilton helps with the feature engineering step. So conceptually we'd try to integration simpler than just creating a task in flyte, with a plugin instead...
The text was updated successfully, but these errors were encountered: