Hello, I am migrating an internal lib that we developped to

kedro==0.18.0

. We use

kedro.framework.session.get_current_session

to get the current session in order to either create a new session if it is None, or use it directly. This function was removed in

0.18.0

(with https://github.com/kedro-org/kedro/pull/1138) . What is the new way to find the current active session?

As per the release notes we have deprecated this functionality https://github.com/kedro-org/kedro/blob/develop/RELEASE.md

OK, so is

session.run

still the best way to run programmatically a pipeline? And if I want to access the context and catalog for a given env, I used to use a session, is it still OK or do I have to find another way?

so my rule of thumb if you're accessing the context directly it's a sign you've gone too far

What do you mean "gone too far"? We have defined datasets in the catalog, and I want to load a dataset. We kedro < 0.18, we used to load the context to access the catalog, and then use

catalog.log

. I do not see how I can use hooks for this use case

so philisophically we believe the nodes should have no knowledge of IO and should be pure python functions

I mean outside of a node

then isn't a

before_pipeline_run

or

after_pipeline_run

hook the right place to do this?

I do not want to run a pipeline, just access the data

Oh okay then in this case it makes sense

An example would be a flask app where an endpoint runs a pipeline, and another makes a plot. The second endpoints needs the catalog

yes with you

OK, I'll have a look, thanks

So I think our change should have remedied that

OK, it seems that I will have to change the API we proposed. We could previously propose:

python
# this would create a session and return the catalog
catalog = get_catalog()
# but this would also return the catalog inside the already created session
with KedroSession.create(env="prod"):
    catalog = get_catalog()

Without access to the current session, I do not see how we can provide it now

Can you not follow this? https://kedro.readthedocs.io/en/stable/kedro_project_setup/session.html

Yes, I know, I am the one providing the

get_catalog

function, as a helper for those that do not remember that you need to do

session.load_context().catalog

. But maybe, it is not that useful

session.run()

would be the preferred way to run a pipeline programatically

Well, ideally, if I am already in a session for some reason, I'd like to use it and not close it

If that's the case using

with KedroSession.create() as session

will probably give you access to one session without the need to close/recreate a new one. The active session will soon be removed and you could create as many sessions as you needed, but most likely you only need one.