You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sedona.apache.org by "Gregoire Leleu (Jira)" <ji...@apache.org> on 2023/02/17 00:08:00 UTC

[jira] [Commented] (SEDONA-244) Align R read/write functions with the Sparklyr framework

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

Gregoire Leleu commented on SEDONA-244:
---------------------------------------

Most sparklyr read functions have a "memory" argument, which it set to true runs
```CACHE TABLE \{table_name}```

Do you see any reason not to implement it?

They also have a "partition" argument, which usually calls ```df.partition(\{num_partitions}``` do we have something similar?

> 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)