You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this release we're announcing two experimental features, namely (1) ArrayNode map tasks, and (2) Execution Tags.
ArrayNode map tasks
ArrayNodes are described more fully in RFC 3346, but the summary is that ArrayNode map tasks are a drop-in replacement for regular map tasks, the only difference being the submodule used to import the map_task function.
More explicitly, let's say you have this code:
Execution tags allow users to can discover their executions and other flyte entities more easily, by creating smarter groupings. The feature is described in this RFC.
As mentioned before, this feature is shipped in an experimental capacity, the idea being that we're going to incorporate the feedback of the community as we iterate. More work is expected to give prominence to the feature in flyteconsole, in the meanwhile, the feature is supported via Remote.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Flyte v1.9.0 Release
In this release we're announcing two experimental features, namely (1) ArrayNode map tasks, and (2) Execution Tags.
ArrayNode map tasks
ArrayNodes are described more fully in RFC 3346, but the summary is that ArrayNode map tasks are a drop-in replacement for regular map tasks, the only difference being the submodule used to import the
map_task
function.More explicitly, let's say you have this code:
In order to switch to using array node map tasks you should import map_task from the
flytekit.experimental
module like so:Execution tags
Execution tags allow users to can discover their executions and other flyte entities more easily, by creating smarter groupings. The feature is described in this RFC.
As mentioned before, this feature is shipped in an experimental capacity, the idea being that we're going to incorporate the feedback of the community as we iterate. More work is expected to give prominence to the feature in flyteconsole, in the meanwhile, the feature is supported via Remote.
Flytekit
FLYTE_SDK_RICH_TRACEBACKS=0
is set by @fg91 in Fix: Disable rich logging handler when env varFLYTE_SDK_RICH_TRACEBACKS=0
is set flytekit#1760Flyteadmin
Flyteplugins
Flytepropeller
Flyteconsole
New Contributors
This discussion was created from the release Flyte v1.9.0 milestone release.
Beta Was this translation helpful? Give feedback.
All reactions