[SPARK-30648][SQL][FOLLOWUP] Refactoring of JsonFilters: move config checking out #29206
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.
What changes were proposed in this pull request?
Refactoring of
JsonFilters:skipRowmethod to check the inputindexspark.sql.json.filterPushdown.enabledfromJsonFilterstoJacksonParser.Why are the changes needed?
JsonFiltersJsonFiltersmakes it consistent withOrderedFilters(see [SPARK-32346][SQL] Support filters pushdown in Avro datasource #29145).JsonFilterscan be used by other datasource in the future and don't depend from the JSON configs.Does this PR introduce any user-facing change?
No
How was this patch tested?
By existing tests suites: