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

Support best-effort JSON parser #7

Open
lowell80 opened this issue Nov 9, 2018 · 0 comments
Open

Support best-effort JSON parser #7

lowell80 opened this issue Nov 9, 2018 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@lowell80
Copy link
Member

lowell80 commented Nov 9, 2018

Add best-effort JSON parsing support to the nested JSON parsing function. It looks like the ijson package may do this, but I haven't tested it. The use case for this functionality is the fact that some nested JSON payloads appear to be subjected to size constraints.

This happens in MS Office 365 Management logs, for example. We should parse whatever we can (best effort) so that some of the data can be retrieved, instead of discarding all of it. I think this lines up with spaths general best-effort approach.

@lowell80 lowell80 added the enhancement New feature or request label Nov 9, 2018
@lowell80 lowell80 added this to the Post 2.0 milestone Nov 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant