Draft: New schema parser - #672
Open
Kriskras99 wants to merge 1 commit into
Open
Conversation
Kriskras99
force-pushed
the
feat/schema_parser_v2
branch
from
September 9, 2026 20:50
c10d80c to
0990ec6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is not ready for review, see it more as a progress update.
The new parser uses a different JSON library
sonicwhich allows the parser to iterate over borrowed strings from the file. This saves a ton of heap allocations.sonicalso has SIMD optimisations whenRUSTFLAGS="-C target-cpu=native"is used, but on the small files we generally have, the impact of that is small.TODO:
Error::new(Details::...))until we're at the edgelarge_schema.asvcRecordWithRequiredFields.avsc