-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Follow up CSV node msg.columns bug #2853 #4610
Labels
Comments
Can you provide a simple flow that demonstrates the issue? |
Hello together, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
see issue #2853:
The issue only occurs if a CSV node is used in a sequence and the columns property of a CSV node is initially empty:
In this case the columns property of a CSV node is set correctly during processing the first part of a sequence.
But the columns property is not updated during the second and other following parts. So, all written data files contain wrong header followed by rows with empty values only.
This behaviour is exactly the same like in closed issue #2853 - obviously the issue was not fixed successfully.
Expected Behavior
For every part in a sequence, the CSV node should not only set the payload to msg.payload but also set the columns property to the current value of msg.columns.
Steps To Reproduce
No response
Example flow
Environment
The text was updated successfully, but these errors were encountered: