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.

[KED-1537] Allow a node input to be a literal value.

See original GitHub issue

I think kedro should add the way to pass a literal to a node, just like they did with param:. Maybe something like literal: or string: and int:

__Originally posted by @sansagara in https://github.com/quantumblacklabs/kedro/issues/213#issuecomment-698932788__

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:2
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
Galileo-Galileicommented, Sep 28, 2020

Hello,

*Disclaimer to the OP: Sorry for the downvote, it is the only way to say that I am against implementing this feature but no offense intended, it is absolutely not personal.

I totally support @WaylonWalker point of view here for everal reasons:

  • I understand why someone want to do this (mainly to iterate faster during their exploration phase), but this will very encourage bad software engineering practice (i.e. tighten compute and configuration by not using a conf file).
  • I know it sounds a bit harsh but I don’t think this feature request is in line with Kedro’s principles (i.e. enforces SE best practices as much as possible).
  • Since the little hack with lamba suggested by @WaylonWalker already works well, I don’t feel it would improve much user experience.
  • This feature will also prevent to track the parameter with a specific name, for logging in mlflow for instance (ok this one is self interested 😇)
2reactions
WaylonWalkercommented, Sep 26, 2020

This would make things simpler, but it is currently possible using partial or lambda functions. See my comment on the previous issue https://github.com/quantumblacklabs/kedro/issues/213#issuecomment-699509279.

If this were implemented I would fear that it would make doing bad things too easy. The current design makes doing the right thing easy (loading from the catalog or params) and doing borderline things possible. I would hate to see a pipeline completely bypass the catalog and pass DataFrames directly into the node.

Read more comments on GitHub >

github_iconTop Results From Across the Web

[KED-1537] Allow a node input to be a literal value. · Issue #526
I think kedro should add the way to pass a literal to a node, just like they did with param:. Maybe something like...
Read more >
How to pass a literal value to a kedro node? - Stack Overflow
One approach would be to pass the data via params. Add column_number: 1 to the parameters.yaml file, and then your node definition would ......
Read more >
HTTPInput node - IBM
This property controls when an input message is parsed. Valid values are On Demand, Immediate, and Complete. By default, this property is set...
Read more >
Custom node parameters aren't set correctly for Expression input
Object created in my application will have the literal value “={{$json[“salutation”]}}” for salutation and “={{$json[“lastName”]}}” for last ...
Read more >
MapVOWL - RML.io
This can be achieved by using a blank node. literal value: The resource denoted by a literal is called its literal value.
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