Some MADlib wrapper functions create result tables that cannot be
dropped in the background, because other functions need to use these
tables. For example,
madlib.arima creates 3 result
tables, which are needed by
predict.arima.css.madlib. One can manually delete these
3 tables when they are not useful anymore using
delete,arima.css.madlib-method. One can also choose to
all such tables created by many such functions together using this
An integer, the connection ID of the database. See
All such result tables created by MADlib wrapper functions start with "__madlib_temp_" followed by three random integers. This function deletes all such tables.
Author: Predictive Analytics Team at Pivotal Inc.
Maintainer: Frank McQuillan, Pivotal Inc. firstname.lastname@example.org
madlib.arima creates three tables with names starting
with "__madlib_temp_" when it fits ARIMA model to time series
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
## Not run: ## set up the database connection ## Assume that .port is port number and .dbname is the database name cid <- db.connect(port = .port, dbname = .dbname, verbose = FALSE) ## use double values as the time stamp ## Any values that can be ordered will work example_time_series <- data.frame( id = seq(0,1000,length.out=length(ts)), val = arima.sim(list(order=c(2,0,1), ar=c(0.7, -0.3), ma=0.2), n=1000000) + 3.2) x <- as.db.data.frame(example_time_series, field.types = list(id="double precision", val = "double precision"), conn.id = cid, verbose = FALSE) dim(x) names(x) ## use formula s <- madlib.arima(val ~ id, x, order = c(2,0,1)) s ## delete all result tables clean.madlib.temp(conn.id = 1) ## s still exists but the 3 tables (model, residuals, etc.) are deleted s db.disconnect(cid, verbose = FALSE) ## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.