[
https://issues.apache.org/jira/browse/SEDONA-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690120#comment-17690120
]
Gregoire Leleu commented on SEDONA-244:
---------------------------------------
Also, if functions reading to typed RDDs are soft deprecated, should we
indicate them as such in R? That means:
* Adding a "deprecated" badge to the documentation
* Adding a soft warning displayed every 8 hours (customizable)
I guess we are talking about:
* sedona_read_shapefile_to_typed_rdd (relies on
_org.apache.sedona.core.formatMapper.shapefileParser.ShapefileReader.readToPolygonRDD)_
* sedona_read_geojson_to_typed_rdd (relies on a
_org.apache.sedona.core.spatialRDD.PolygonRDD_ constructor, not a FormatMapper)
* sedona_read_dsv_to_typed_rdd: this one has no "non-typed" version __
> 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)
