[SEDONA-440] Enable nested predicate pushdown support for GeoParquet #1165
Conversation
This file contains 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
|
This PR will fix opengeospatial/geoparquet#192 |
Kontinuation
force-pushed
the
geoparquet-pushdown-nested-column
branch
from
f52213b
to
eceb78a
Compare
jiayuasu
approved these changes
Dec 29, 2023
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.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject.What changes were proposed in this PR?
File formats that support nested predicate pushdown are configured by
spark.sql.optimizer.nestedPredicatePushdown.supportedFileSources, a comma-separated list of data source names. The default value isparquet,orc. This patch appends "geoparquet" to the list when creating SedonaContext to enable nested predicate pushdown for GeoParquet.How was this patch tested?
Add a new test case.
Did this PR include necessary documentation updates?