[jira] [Commented] (SEDONA-85) Add ST_GeoHash to Sedona flink streaming.
[ https://issues.apache.org/jira/browse/SEDONA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504411#comment-17504411 ] Paweł Kociński commented on SEDONA-85: -- [~malka] Flink has really poor support for Python at the moment. Thats why I added tests for Pyspark streaming to make sure that works fine. GeoHash function is done that way, we have base code in sql module but in sql fuinction we call it only and I was able to easily reuse that in Flink. > Add ST_GeoHash to Sedona flink streaming. > - > > Key: SEDONA-85 > URL: https://issues.apache.org/jira/browse/SEDONA-85 > Project: Apache Sedona > Issue Type: Improvement >Reporter: Paweł Kociński >Assignee: Paweł Kociński >Priority: High > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SEDONA-85) Add ST_GeoHash to Sedona flink streaming.
[ https://issues.apache.org/jira/browse/SEDONA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504399#comment-17504399 ] Netanel Malka commented on SEDONA-85: - [~jiayu] I am wondering if we can generalize the SQL functions and create something like a core functions that both spark and flink can use (and another modules will be use in the future). I thought about putting the actual implementation of the geo functions in a core module, and Spark and Flink will only call those functions. What do you think? [~imbruced] Is that means that we will need to rewrite the python API? > Add ST_GeoHash to Sedona flink streaming. > - > > Key: SEDONA-85 > URL: https://issues.apache.org/jira/browse/SEDONA-85 > Project: Apache Sedona > Issue Type: Improvement >Reporter: Paweł Kociński >Assignee: Paweł Kociński >Priority: High > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
