Open
Conversation
changes: * `ParseSpec` and all of its implementations have been removed, including `JavascriptParseSpec` and `JSONLowercaseParseSpec`, which have no `InputFormat` equivalents * migrated all tests which were still using `ParseSpec` to convert into a normal schema + input format to just use `InputFormat` directly instead * `FlattenJSONBenchmark` now measures the `JsonInputFormat` instead of using a json parse spec/parser
gianm
approved these changes
Mar 31, 2026
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.
changes:
ParseSpecand all of its implementations have been removed, includingJavascriptParseSpecandJSONLowercaseParseSpec, which have noInputFormatequivalentsParseSpecto convert into a normal schema + input format to just useInputFormatdirectly insteadFlattenJSONBenchmarknow measures theJsonInputFormatinstead of using a json parse spec/parser