-
Notifications
You must be signed in to change notification settings - Fork 61
feature; catalog metadata and caching status published in node events #70
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any versions you need to bump?
Updated now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no version bump is okay?
also, we're sure we want a different node metadata for every node type right? not a generic nodemetadata message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
merge master or rebase, update setup.py, add comment.
@@ -10,6 +10,7 @@ enum ResourceType { | |||
TASK = 1; | |||
WORKFLOW = 2; | |||
LAUNCH_PLAN = 3; | |||
DATASET = 4; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One of these things is not like the other. Can we at least add a comment explaining why there is something that looks different here? Also, could we create a GH issue if there isn't one to merge all the proto objects in data catalog https://github.com/lyft/datacatalog/blob/master/protos/idl/service.proto into this repo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed
…#70) * Catalog store handling * Event proto updated * generated * merged * Dataset Identifier changed * Better model * Exposing TaskNodeMetadata with catalog information in the API * 0.17.38 * Comment * docs updated
TL;DR
Caching Information is currently not available in the UI or CLI. This hinders user productivity. This PR sets up the flow of data between propeller and admin. Once the data is published, next step would be to expose it through the API
Type
Are all requirements met?
Tracking Issue
flyteorg/flyte#138
Follow-up issue
flyteorg/flyte#71