[jira] [Created] (SEDONA-502) SpatialRDD's indexedRDD is not available in RangeQuery and KNNQuery
Guanli Liu created SEDONA-502:
-
Summary: SpatialRDD's indexedRDD is not available in RangeQuery
and KNNQuery
Key: SEDONA-502
URL: https://issues.apache.org/jira/browse/SEDONA-502
Project: Apache Sedona
Issue Type: Bug
Reporter: Guanli Liu
I encountered a problem while executing queries. I loaded a set of point data,
followed by partitioning and building an index on each partition. However, when
I performed range queries and KNN queries, errors occurred. After inspecting
the source code, I found that the reason was the indexedRawRDD and indexedRDD.
When creating indexes on all partitions of a SpatialRDD object:
{code:java}
// create quadtree partition
point_rdd.spatialPartitioning(GridType.QUADTREE)
// create rtree index
point_rdd.buildIndex(IndexType.RTREE, True) {code}
The following error message is shown:
{code:java}
org.apache.sedona.core.spatialOperator.RangeQuery.SpatialRangeQuery.
: java.lang.Exception: [RangeQuery][SpatialRangeQuery] Index doesn't exist.
Please build index on rawSpatialRDD
...{code}
The reason is when building an index on each partition of a SpatialRDD object,
indexedRDD should be used instead of indexedRawRDD (which is null).
indexedRawRDD can be used when building an index on rawSpatialRDD.
{code:java}
// From Line 61 at org.apache.sedona.core.spatialOperator.RangeQuery.java
if (useIndex == true) {
if (spatialRDD.indexedRawRDD == null) {
throw new Exception("[RangeQuery][SpatialRangeQuery] Index doesn't
exist. Please build index on rawSpatialRDD.");
}
return spatialRDD.indexedRawRDD.mapPartitions(new
RangeFilterUsingIndex(queryGeometry, spatialPredicate));
}{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [DOCS] Fix spelling in `binder/Sedona_OvertureMaps_GeoParquet.ipynb` [sedona]
jiayuasu merged PR #1249: URL: https://github.com/apache/sedona/pull/1249 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-501] ST_Split maps to wrong Java-call [sedona]
jiayuasu merged PR #1252: URL: https://github.com/apache/sedona/pull/1252 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-501] ST_Split maps to wrong Java-call [sedona]
niklas-petersen opened a new pull request, #1252: URL: https://github.com/apache/sedona/pull/1252 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Map Python ST_Split to Java ST_Split. ## How was this patch tested? I updated unit tests. I could not get the polygon/polygon test dataset to yield a deterministic result, so I added a test data that is identical to the documentation example: https://sedona.apache.org/1.5.1/api/sql/Function/?h=st_#st_split ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SEDONA-501) ST_Split maps to wrong Java-call
Niklas Loevenholdt Petersen created SEDONA-501: -- Summary: ST_Split maps to wrong Java-call Key: SEDONA-501 URL: https://issues.apache.org/jira/browse/SEDONA-501 Project: Apache Sedona Issue Type: Bug Affects Versions: 1.5.1 Reporter: Niklas Loevenholdt Petersen Fix For: 1.6.0 When using the Python ST_Split (from sedona.sql.st_functions) you get quite a different result then using ST_Split in a SQL statement. The ST_Split seems to be mapped to the wrong Java-call (ST_SymDifference). I am happy to have a go on fixing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [I] fieldNames - AttributeError: Not available before 1.0.0 sedona version [sedona]
AlexTelloG closed issue #1247: fieldNames - AttributeError: Not available before 1.0.0 sedona version URL: https://github.com/apache/sedona/issues/1247 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
