The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
An interface to 'Azure CosmosDB': <https://azure.microsoft.com/en-us/services/cosmos-db/>. On the admin side, 'AzureCosmosR' provides functionality to create and manage 'Cosmos DB' instances in Microsoft's 'Azure' cloud. On the client side, it provides an interface to the 'Cosmos DB' SQL API, letting the user store and query documents and attachments in 'Cosmos DB'. Part of the 'AzureR' family of packages.
Version: | 1.0.0 |
Depends: | R (≥ 3.3) |
Imports: | utils, AzureRMR (≥ 2.3.3), curl, openssl, jsonlite, httr, uuid, vctrs (≥ 0.3.0) |
Suggests: | AzureTableStor, mongolite, DBI, odbc, dplyr, testthat, knitr, rmarkdown |
Published: | 2021-01-18 |
DOI: | 10.32614/CRAN.package.AzureCosmosR |
Author: | Hong Ooi [aut, cre], Andrew Liu [ctb] (Assistance with Cosmos DB), Microsoft [cph] |
Maintainer: | Hong Ooi <hongooi73 at gmail.com> |
BugReports: | https://github.com/Azure/AzureCosmosR/issues |
License: | MIT + file LICENSE |
URL: | https://github.com/Azure/AzureCosmosR https://github.com/Azure/AzureR |
NeedsCompilation: | no |
Materials: | README NEWS |
In views: | WebTechnologies |
CRAN checks: | AzureCosmosR results |
Reference manual: | AzureCosmosR.pdf |
Vignettes: |
AzureCosmosR |
Package source: | AzureCosmosR_1.0.0.tar.gz |
Windows binaries: | r-devel: AzureCosmosR_1.0.0.zip, r-release: AzureCosmosR_1.0.0.zip, r-oldrel: AzureCosmosR_1.0.0.zip |
macOS binaries: | r-release (arm64): AzureCosmosR_1.0.0.tgz, r-oldrel (arm64): AzureCosmosR_1.0.0.tgz, r-release (x86_64): AzureCosmosR_1.0.0.tgz, r-oldrel (x86_64): AzureCosmosR_1.0.0.tgz |
Please use the canonical form https://CRAN.R-project.org/package=AzureCosmosR to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.