Anyone have any experience adding caching to `map_...
# announcements
t
Anyone have any experience adding caching to
map_task
? I've tried by adding the caching stuff to the
@task
decorator and in the "mapification" like this:
Copy code
map_task(my_task)(input=input).with_overrides(cache=True, cache_version="1.0")
but I'm not seeing in the flyte console the little swirly that indicates the task either wrote to or read from the cache. Is caching a map task supported?
d
Hi @Thomas Addison, great question. map tasks do support caching. We have been doing a lot of work recently to update the UI visualizations of map tasks. I know that the caching visualizations should be working. What version of Flyte are you currently running?
t
we're running 0.19.4 i think
upon further investigation, it does look like the map task is caching even though the little swirly isn't present in the ui
d
Oh OK perfect. Thanks for looking a bit deeper at this! @Nastya Rusina can you confirm that a version update would pick up everything necessary to display map task cache writes / hits in the UI?
n
I believe it will. But let me check it locally first. I will get back with answer here shortly :)
@Thomas Addison It looks like it is present in latest flyteconsole.
t
awesome, thanks for looking into it. looking forward to when we upgrade console to see that cool cache swirly
🙂 1
n
I’m sorry @Thomas Addison it looks like I misled you. Further investigation showed that we don’t see swirly thing on caching tasks when perform them locally. The new issue was created to fix it: #514 We currently looking at it more deeply. Sorry again for confusion 🙇‍♀️
The fix for this issue just merged into master. From FlyteConsole v.1.1.4 (not released yet) mapped task will have a partially cached icon, and you would be able to see cache status per each task in array.
🦜 1
t
cool! ty!
109 Views