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

stdin segment fails on additional/no line breaks in json #83

Open
Mynacol opened this issue Nov 19, 2024 · 0 comments
Open

stdin segment fails on additional/no line breaks in json #83

Mynacol opened this issue Nov 19, 2024 · 0 comments

Comments

@Mynacol
Copy link
Collaborator

Mynacol commented Nov 19, 2024

I modified a json export with another tool (jq) and was unable to read it back into flowpipeline.
In the first attempt, jq pretty-printed the json with newlines between each json field (not a full flowpipeline object), which lead to a failure decoding the json.
In the second attempt I instructed jq to "uglify" the json, which removes all newlines. But then the import fails because the file contains one very long line, leading to a "buffer too big" error.

Both errors are caused by the input segment using a scanner and always processing the data line-by-line. This however is only successful for a subset of valid json files.

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

1 participant