[KED-1537] Allow a node input to be a literal value.
See original GitHub issueI 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:
- Created 3 years ago
- Reactions:2
- Comments:7 (5 by maintainers)
Top 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 >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

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:
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.