[ 
https://issues.apache.org/jira/browse/SEDONA-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690512#comment-17690512
 ] 

Jia Yu commented on SEDONA-244:
-------------------------------

[~gregleleu] Your suggestion makes perfect sense to me.

 

Let's do this!
 * Functions that return a DF like the rest of the ecosystem: 
spark_read_\{geoparquet|geojson|shapefile|geotiff|...}
 * Functions that return an RDD: sedona_read_\{wkt|wkb|shapefile|geojson}

 

Let's do this too!
 * Adding a "deprecated" badge to the documentation
 * Adding a soft warning displayed every 8 hours (customizable)

> Align R read/write functions with the Sparklyr framework
> --------------------------------------------------------
>
>                 Key: SEDONA-244
>                 URL: https://issues.apache.org/jira/browse/SEDONA-244
>             Project: Apache Sedona
>          Issue Type: Improvement
>            Reporter: Gregoire Leleu
>            Priority: Major
>
> Apache Sedona in R works as an extension of Sparklyr. Read/write functions 
> for Sedona should follow the same overall format than the rest of the 
> framework. E.g. :
>  * Type of return value (I believe a tbl)
>  * Standard arguments: name, path, memory, repartition...
>  * Standard behavior: overwrite, default names etc.
> Currently some functions in R sedona return RDDs that need to be registered 
> as sdf.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to