Skip to content

Commit

Permalink
Prepare for CRAN release
Browse files Browse the repository at this point in the history
  • Loading branch information
ianmcook committed Feb 5, 2024
1 parent 8c6d2e5 commit af55a7b
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 35 deletions.
2 changes: 1 addition & 1 deletion DESCRIPTION
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Package: implyr
Type: Package
Title: R Interface for Apache Impala
Version: 0.4.0.9002
Version: 0.5.0
Authors@R: c(
person("Ian", "Cook", email = "[email protected]", role = c("aut", "cre")),
person(family = "Cloudera", role = c("cph"))
Expand Down
4 changes: 2 additions & 2 deletions NEWS.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# implyr (development version)
# implyr 0.5.0

* Suppressed an object not found warning (#51)
* Updated for compatibility with dbplyr 0.4.0 (#59, @liudvikasakelis)
* Updated for compatibility with dbplyr 2.4.0 (#59, @liudvikasakelis)
* Required newer versions of Depends and Imports packages

# implyr 0.4.0
Expand Down
5 changes: 0 additions & 5 deletions README.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,6 @@ knitr::opts_chunk$set(

# implyr <img src="man/figures/logo.png" align="right" height="139" />

<!-- badges: start -->
[![Build Status](https://travis-ci.org/ianmcook/implyr.svg?branch=master)](https://travis-ci.org/ianmcook/implyr)
[![CRAN_Status_Badge](https://www.r-pkg.org/badges/version/implyr)](https://cran.r-project.org/package=implyr)
<!-- badges: end -->

## Overview

**implyr** is a SQL backend to [dplyr](https://cran.r-project.org/package=dplyr) for [Apache Impala](https://impala.apache.org), the massively parallel processing query engine. Impala enables low-latency SQL queries on large datasets stored in HDFS, Apache HBase, Apache Kudu, Amazon S3, Microsoft ADLS, and Dell EMC Isilon.
Expand Down
47 changes: 20 additions & 27 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,6 @@

# implyr <img src="man/figures/logo.png" align="right" height="139" />

<!-- badges: start -->

[![Build
Status](https://travis-ci.org/ianmcook/implyr.svg?branch=master)](https://travis-ci.org/ianmcook/implyr)
[![CRAN\_Status\_Badge](https://www.r-pkg.org/badges/version/implyr)](https://cran.r-project.org/package=implyr)
<!-- badges: end -->

## Overview

**implyr** is a SQL backend to
Expand Down Expand Up @@ -300,14 +293,14 @@ Like other SQL backends to dplyr, implyr delays work until a result
needs to be computed, then computes the result as a single query
operation.

- Use `collect()` to execute the query and return the result to R as a
data frame `tbl`.
- Use `as.data.frame()` to execute the query and return the result to
R as an ordinary data frame.
- Use `compute(temporary = FALSE)` to execute the query and store the
result in an Impala table. Impala does not support temporary tables,
so `temporary = FALSE` is required.
- Use `collapse()` to generate the query for later execution.
- Use `collect()` to execute the query and return the result to R as a
data frame `tbl`.
- Use `as.data.frame()` to execute the query and return the result to R
as an ordinary data frame.
- Use `compute(temporary = FALSE)` to execute the query and store the
result in an Impala table. Impala does not support temporary tables,
so `temporary = FALSE` is required.
- Use `collapse()` to generate the query for later execution.

If you print or store a result without using one of these functions,
then implyr returns a lazy `tbl`. Only use `collect()` or
Expand Down Expand Up @@ -534,17 +527,17 @@ uses parallel processing and stores data in multiple files, so the the
notion of data being stored in sorted order is impractical. This has
several important implications for the use of implyr:

- Rows are not necessarily returned in the same order that they were
in when added to Impala. To return rows in a specific order, you
must use `arrange()`.
- If row ordering is applied in an intermediate phase of query
processing, Impala may not return the final result in sorted order.
To ensure that results are in sorted order, apply `arrange()` last,
after all other dplyr verbs. implyr will issue a warning if you
apply `arrange()` in an earlier step.
- When using `compute()` to store results in an Impala table, Impala
may not preserve row order. implyr will issue a warning if you use
`arrange()` before `compute()`.
- Rows are not necessarily returned in the same order that they were in
when added to Impala. To return rows in a specific order, you must use
`arrange()`.
- If row ordering is applied in an intermediate phase of query
processing, Impala may not return the final result in sorted order. To
ensure that results are in sorted order, apply `arrange()` last, after
all other dplyr verbs. implyr will issue a warning if you apply
`arrange()` in an earlier step.
- When using `compute()` to store results in an Impala table, Impala may
not preserve row order. implyr will issue a warning if you use
`arrange()` before `compute()`.

See the [Impala ORDER BY
documentation](https://docs.cloudera.com/documentation/enterprise/latest/topics/impala_order_by.html)
Expand Down Expand Up @@ -588,7 +581,7 @@ intermediate result will be small enough to fit in memory in your R
session.

The `median()` function returns a value that is approximately (not
necessarily exactly) the median. See [APPX\_MEDIAN
necessarily exactly) the median. See [APPX_MEDIAN
Function](https://docs.cloudera.com/documentation/enterprise/latest/topics/impala_appx_median.html).

implyr supports some Impala functions that are not specified by R or by
Expand Down

0 comments on commit af55a7b

Please sign in to comment.