Feature Area
/area backend
What feature would you like to see?
I would like that variables returned by a cell is transformed into output artifacts automatically.
What is the use case or pain point?
Let's say my notebook results into a variable that I would like to make it accessible to users. Currently I have to add a task just to print that variable, so Kale creates an output artifact which I can download. See this example:
I had to create a new step, but what I wanted was to access the chroma_db object. It would be great if I have a way to make it as an output parameter automatically or using a new property in pipeline which we can use identify the "result artifact" without the need of create a new cell.
Is there a workaround currently?
Create a cell just to make it sure that Kale will serialize and pass the result variable as an artifact and we will be able to download it.
Love this idea? Give it a 👍.
Feature Area
/area backend
What feature would you like to see?
I would like that variables returned by a cell is transformed into output artifacts automatically.
What is the use case or pain point?
Let's say my notebook results into a variable that I would like to make it accessible to users. Currently I have to add a task just to print that variable, so Kale creates an output artifact which I can download. See this example:
I had to create a new step, but what I wanted was to access the chroma_db object. It would be great if I have a way to make it as an output parameter automatically or using a new property in pipeline which we can use identify the "result artifact" without the need of create a new cell.
Is there a workaround currently?
Create a cell just to make it sure that Kale will serialize and pass the result variable as an artifact and we will be able to download it.
Love this idea? Give it a 👍.