We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe.
The current json codec supports parsing JSON arrays. However, many users would like to parse ndjson formatted files.
json
{"key": "value1"} {"key": "value2"} {"key": "value3"} {"key": "value4"}
Describe the solution you'd like
Create a new codec: ndjson.
ndjson
Describe alternatives you've considered (Optional)
We can already ready nd-json files using a combination of:
parse_json
The text was updated successfully, but these errors were encountered:
Additionally, we have seen a number of situations where JSON objects are not always properly separated by a newline.
I believe we can implement this codec to have a loose enforcement of different objects by default. Thus allowing for parsing the following:
{"key": "value1"} {"key": "value2"}{"key": "value3"} {"key": "value4"} {"key": "value5"} {"key": "value6"} {"key": "value7"}
This would produce seven events.
This change would also provide something that isn't currently possible with the newline codec and parse_json combination.
newline
Sorry, something went wrong.
dlvenable
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
The current
json
codec supports parsing JSON arrays. However, many users would like to parse ndjson formatted files.Describe the solution you'd like
Create a new codec:
ndjson
.Describe alternatives you've considered (Optional)
We can already ready nd-json files using a combination of:
parse_json
processor.The text was updated successfully, but these errors were encountered: