Erick Figueiredo
02/27/2025, 4:30 PMHall
02/27/2025, 4:30 PMLaura Couto
02/27/2025, 5:24 PMErick Figueiredo
02/27/2025, 5:27 PMLaura Couto
02/27/2025, 5:30 PMErick Figueiredo
02/27/2025, 5:39 PMTakieddine Kadiri
02/27/2025, 6:55 PMyour_session.run(inputs={‘your_kedro_dataset’:your_endpoint_data})
From there it’s up to you to define the right dataset type, depending on the data that would be injected in it.
Could you please elaborate more on your use case or share with us your code ?Erick Figueiredo
02/27/2025, 7:03 PMErick Figueiredo
02/27/2025, 7:09 PMTakieddine Kadiri
02/27/2025, 7:23 PMinputs={'messages': messages}
With maybe some formating of your Messages object into a json object before running the session.
Under the hood kedro-boot replace your json dataset with a memorydataset containing your endpoint messages data. This is done at every API requests, in fact an all new catalog is created at every API request.
So there is no need to persist you data so the Json dataset could access it.
Let me know if it’s clear and if it’s works for youErick Figueiredo
02/27/2025, 7:46 PM