Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Map Values is not working when it receives NULL as input #338

Closed
JhansiBonthu opened this issue Nov 6, 2020 · 2 comments
Closed
Assignees
Milestone

Comments

@JhansiBonthu
Copy link

JhansiBonthu commented Nov 6, 2020

In some scenarios,we don't have data for the mapped one's so in that case input value is null.

To Reproduce
Steps to reproduce the behavior:
1.Attachedzip file,which has sample graphs to reproduce it.
2. No need to ingest any data to test this scenario.
Graph_Errors.zip

Error1 :
Error during graph execution. Check the log for details: Cannot read property 'toString' of null
Error2: when we use lookup data as input
Error during graph execution. Check the log for details: Cannot read property 'toString' of undefined

@josvanroosmalen josvanroosmalen added this to the 2.0.1 milestone Nov 6, 2020
@josvanroosmalen josvanroosmalen self-assigned this Nov 6, 2020
@josvanroosmalen
Copy link
Collaborator

Default input is also not working. In addition casting is not working ok. Will fix this as well.

Cast to bool -> cast to bool or false in case can't be casted
Cast to number -> cast to number or -1 in case NaN

josvanroosmalen pushed a commit that referenced this issue Nov 6, 2020
@josvanroosmalen
Copy link
Collaborator

shipping 2.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants