[GitHub] [incubator-sedona] jiayuasu commented on pull request #708: [SEDONA-189] Prepare geometries in broadcast join
jiayuasu commented on PR #708: URL: https://github.com/apache/incubator-sedona/pull/708#issuecomment-1304402415 @umartin Hi Martin, is this PreparedGeometry related to your https://issues.apache.org/jira/browse/SEDONA-178 ? -- 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] [Commented] (SEDONA-184) ScatterPlot fails to generate vector image
[ https://issues.apache.org/jira/browse/SEDONA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17629250#comment-17629250 ] Jia Yu commented on SEDONA-184: --- Vector image generation (SVG) has been removed since we moved GeoSpark to Apache Software Foundation due to the incompatible license of the SVG generator lib. > ScatterPlot fails to generate vector image > -- > > Key: SEDONA-184 > URL: https://issues.apache.org/jira/browse/SEDONA-184 > Project: Apache Sedona > Issue Type: Bug > Environment: VirtualBox guest: 24GB RAM, 8vCore, Debian 9, Java > 8-201, Netbeans 8.2, Hadoop 2.10.0, Spark 2.4.8 >Reporter: Theofilos Ioannidis >Priority: High > Labels: Image, Vector, Viz > > In the Viz showcase example, the ScatterPlot fails to generate vector image. > It seems to me that the last parameter 'generateVectorImage' of the > constructor public ScatterPlot(int resolutionX, int resolutionY, Envelope > datasetBoundary, boolean reverseSpatialCoordinate, boolean > generateVectorImage) is ignored at the ScatterPlot class level and at the > superclass VisualizationOperator level. > The constructor public VisualizationOperator(int resolutionX, int > resolutionY, Envelope datasetBoundary, ColorizeOption colorizeOption, boolean > reverseSpatialCoordinate, > int partitionX, int partitionY, boolean parallelPhotoFilter, > boolean parallelRenderImage, boolean generateVectorImage) does not handle the > parameter 'generateVectorImage' at all. > I am working with commit 0a6f26a0e0eace87243dd919738af5f182557b8a > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [incubator-sedona] tanelk opened a new pull request, #708: [SEDONA-189] Prepare geometries in broadcast join
tanelk opened a new pull request, #708: URL: https://github.com/apache/incubator-sedona/pull/708 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the assoicated 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? Use prepared geometries in `BroadcastIndexJoinExec` to speed up queries. ## How was this patch tested? Running the existing UTs in sql submodule ## 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-189) Using prepared geometries
Tanel Kiis created SEDONA-189: - Summary: Using prepared geometries Key: SEDONA-189 URL: https://issues.apache.org/jira/browse/SEDONA-189 Project: Apache Sedona Issue Type: Improvement Reporter: Tanel Kiis With complex polygons using prepared geometries can improve query performance by an order of magnitude. A test, where I had 1M points and 5k polygons, a simple broadcast join and count with ST_Contains had a performance increase from 1m 20s down to 10s (8x improvement). -- This message was sent by Atlassian Jira (v8.20.10#820010)
