question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Running a specific node using tags in 0.17.2

See original GitHub issue

Introduction

I’m looking to run a specific node, following instructions [here], for testing purposes. Not sure I’d need to register this pipeline to be able to do that… (https://kedro.readthedocs.io/en/stable/06_nodes_and_pipelines/01_nodes.html?highlight=tags#how-to-tag-a-node). Anyhow, I created a new environment and started a new project using kedro new pandas-iris. Next I added an example pipeline with a node I’d like to test using tags.

I add the following line to src/{{ project name }}/pipelines/data_science/pipeline.py: def test_pipeline(**kwargs): return Pipeline([node(lambda x: x,"example_train_x","example_model",name="test",tags="test")]

Next, I try to run the specific node using kedro run --tag test and get the error image

Question

Is there something I’m missing here? Do I need to follow certain steps after generating pandas-iris, specific to pipeline registry? How can I run the nodes tagged with test? I think the default pipeline error may be linked to this

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
WaylonWalkercommented, Mar 23, 2021

Whether this turns out as user error or not the Error message here is quite confusing and not very helpful.

If I render a new kedro template with 0l17.2 and delete my pipeline_registry.py module I get the same error. In this case the error should guide the user to create a register_pipelines function in the appropriate module

If I rename __default__ to new I get the same error. In this case the error should make its best attempt to guide the user to the module with the register_pipelines function and add a __default__ key.

1reaction
WaylonWalkercommented, Mar 23, 2021

The error you are seeing is due to improperly formatted pipelines dictionary, or a missing register_pipelines function.

Are you using pipeline_registry.py or hooks.py?

Look in either of those modules for a function called register_pipelines. It should return a dictionary of pipelines, one must be found under the key __default__

Read more comments on GitHub >

github_iconTop Results From Across the Web

Running a specific node using tags in 0.17.2 · Issue #733
I'm looking to run a specific node, following instructions [here], for testing purposes. Not sure I'd need to register this pipeline to be...
Read more >
Frequently asked questions — Kedro 0.17.2 documentation
Add and remove project-specific dependencies ... pipeline with tagged nodes · Slice a pipeline by running specified nodes · How to recreate missing...
Read more >
Target nodes spec
Dkron has the ability to run jobs in specific nodes by leveraging the use of tags. You can choose whether a job is...
Read more >
1.1.7 (core) / 0.17.7 (libraries)
This resolves an issue where retrieving the available tags could cause significant performance problems. Tags can still be searched with freeform text, and...
Read more >
raneto
Latest version: 0.17.2, last published: a month ago. Start using raneto in your project by running `npm i raneto`. ... Current Tags. Version....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found