[GH-3020] Add ST_H3ToParent - #3310
Merged
Merged
Conversation
1 task
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.
Did you read the Contributor Guide?
Is this PR related to a ticket?
[GH-3020] Add ST_H3ToParent.Related to #3020.
This PR intentionally implements only
ST_H3ToParentas the first incremental part of the H3 hierarchy functions requested in #3020. It does not close the parent issue.What changes were proposed in this PR?
ST_H3ToParentbacked by H3'scellToParent.The function accepts an H3 cell and a target parent resolution and returns the corresponding parent H3 cell. Null inputs are propagated by the SQL integrations.
How was this patch tested?
mvn spotless:applymvn -pl common -Dtest=FunctionsTest#h3ToParent testmvn -pl spark/common -DwildcardSuites=org.apache.sedona.sql.functions.STH3Functions org.scalatest:scalatest-maven-plugin:2.2.0:testmvn -pl flink -Dtest=FunctionTest#testH3ToParent testpython -m py_compile python/sedona/spark/sql/st_functions.py python/tests/sql/test_function.py python/tests/sql/test_dataframe_api.pygit diff --checkThe Python Spark integration tests were not run locally because PySpark is not installed in the local Python environment. The corresponding Python files passed bytecode compilation, and the underlying Spark SQL expression was covered by the JVM Spark test suite.
Did this PR include necessary documentation updates?
v2.0.0.