Pivotal Knowledge Base

Follow

How to install or uninstall MADlib

Environment

Product Version
Pivotal Greenplum (GPDB) 4.3.x,4.2.x
OS RHEL 6.x
Others  

 

Purpose 

This article explains how to install and uninstall MADlib in a GPDB database.

 

Procedure

Installation

  1. Log on to the product download website and download the necessary MADlib package from the Analytics section. For additional information on how to use the site to download the product, check this link.  
  2. Once the download is completed, source the Greenplum home as shown below:
source /usr/local/greenplum-db/greenplum_path.sh

    3. Untar the file.

Please note: In this example, we will be trying to install the MADlib package "madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.tar": replace the file name according to the package that you will be attempting to install.

tar -xvf madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.tar

    4. Using gppkg , install the MADlib rpm.

[gpadmin@mdw tmp]$ gppkg -i GPDB_4.3/madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg
20150419:07:20:23:007200 gppkg:mdw:gpadmin-[INFO]:-Starting gppkg with args: -i GPDB_4.3/madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg
20150419:07:20:23:007200 gppkg:mdw:gpadmin-[INFO]:-Installing package madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg
20150419:07:20:23:007200 gppkg:mdw:gpadmin-[INFO]:-Validating rpm installation cmdStr='rpm --test -i /usr/local/greenplum-db-4.3.4.0/.tmp/madlib-1.7-1.x86_64.rpm --dbpath /usr/local/greenplum-db-4.3.4.0/share/packages/database --prefix /usr/local/greenplum-db-4.3.4.0'
20150419:07:20:26:007200 gppkg:mdw:gpadmin-[INFO]:-Installing madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg locally
20150419:07:20:26:007200 gppkg:mdw:gpadmin-[INFO]:-Validating rpm installation cmdStr='rpm --test -i /usr/local/greenplum-db-4.3.4.0/.tmp/madlib-1.7-1.x86_64.rpm --dbpath /usr/local/greenplum-db-4.3.4.0/share/packages/database --prefix /usr/local/greenplum-db-4.3.4.0'
20150419:07:20:26:007200 gppkg:mdw:gpadmin-[INFO]:-Installing rpms cmdStr='rpm -i /usr/local/greenplum-db-4.3.4.0/.tmp/madlib-1.7-1.x86_64.rpm --dbpath /usr/local/greenplum-db-4.3.4.0/share/packages/database --prefix=/usr/local/greenplum-db-4.3.4.0'
20150419:07:20:27:007200 gppkg:mdw:gpadmin-[INFO]:-Completed local installation of madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg.
20150419:07:20:27:007200 gppkg:mdw:gpadmin-[INFO]:-Please run the following command to deploy MADlib
usage:  madpack install [-s schema_name] -p greenplum -c user@host:port/database
Example:
       $ $GPHOME/madlib/bin/madpack install -s madlib -p greenplum -c gpadmin@mdw:5432/testdb
       This will install MADlib objects into a Greenplum database named "testdb"
       running on server "mdw" on port 5432. Installer will try to login as "gpadmin"
       and will prompt for password. The target schema will be "madlib".
       To upgrade to a new version of MADlib from version v1.0 or later, use option "upgrade",
       instead of "install"
For additional options run:
$ madpack --help
Release notes and additional documentation can be found at http://madlib.net
20150419:07:20:27:007200 gppkg:mdw:gpadmin-[INFO]:-madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg successfully installed.

   5. Once completed , install the MADlib function in the database, using the following command (check that the port (5432) and database(flightdata) correspond to your cluster):

[gpadmin@mdw tmp]$ $GPHOME/madlib/bin/madpack install -s madlib -p greenplum -c gpadmin@mdw:5432/flightdata
Password for user gpadmin:
madpack.py : INFO : Detected Greenplum DB version 4.3.
madpack.py : INFO : *** Installing MADlib ***
madpack.py : INFO : MADlib tools version    = 1.7 (/usr/local/greenplum-db-4.3.4.0/madlib/Versions/1.7/bin/../madpack/madpack.py)
madpack.py : INFO : MADlib database version = None (host=mdw:5432, db=flightdata, schema=madlib)
madpack.py : INFO : Testing PL/Python environment...
madpack.py : INFO : > Creating language PL/Python...
madpack.py : INFO : > PL/Python environment OK (version: 2.6.2)
madpack.py : INFO : Installing MADlib into MADLIB schema...
madpack.py : INFO : > Creating MADLIB schema
madpack.py : INFO : > Creating MADLIB.MigrationHistory table
madpack.py : INFO : > Writing version info in MigrationHistory table
madpack.py : INFO : > Creating objects for modules:
madpack.py : INFO : > - array_ops
madpack.py : INFO : > - bayes
madpack.py : INFO : > - crf
madpack.py : INFO : > - elastic_net
madpack.py : INFO : > - linalg
madpack.py : INFO : > - pmml
madpack.py : INFO : > - prob
madpack.py : INFO : > - quantile
madpack.py : INFO : > - sketch
madpack.py : INFO : > - stats
madpack.py : INFO : > - svd_mf
madpack.py : INFO : > - svec
madpack.py : INFO : > - tsa
madpack.py : INFO : > - conjugate_gradient
madpack.py : INFO : > - data_profile
madpack.py : INFO : > - lda
madpack.py : INFO : > - svec_util
madpack.py : INFO : > - utilities
madpack.py : INFO : > - assoc_rules
madpack.py : INFO : > - cart
madpack.py : INFO : > - convex
madpack.py : INFO : > - glm
madpack.py : INFO : > - kernel_machines
madpack.py : INFO : > - linear_systems
madpack.py : INFO : > - recursive_partitioning
madpack.py : INFO : > - regress
madpack.py : INFO : > - sample
madpack.py : INFO : > - summary
madpack.py : INFO : > - kmeans
madpack.py : INFO : > - pca
madpack.py : INFO : > - validation
madpack.py : INFO : MADlib 1.7 installed successfully in MADLIB schema.

   6. Verify the installation. 

  • Run the install-check switch under the madpack executable to verify the installation. This would take 10-15 minutes to complete. Once it is finished, verify that all the TEST RESULTs have the PASS status.
[gpadmin@mdw tmp]$ $GPHOME/madlib/bin/madpack install-check -p greenplum -c gpadmin@mdw:5432/flightdata
madpack.py : INFO : Detected Greenplum DB version 4.3.
TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 274 milliseconds
TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 2261 milliseconds
TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 6847 milliseconds
TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 2463 milliseconds
TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 3544 milliseconds
TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 2702 milliseconds
[....]
[....]
TEST CASE RESULT|Module: sample|sample.sql_in|PASS|Time: 382 milliseconds
TEST CASE RESULT|Module: summary|summary.sql_in|PASS|Time: 1531 milliseconds
TEST CASE RESULT|Module: kmeans|kmeans.sql_in|PASS|Time: 5192 milliseconds
TEST CASE RESULT|Module: pca|pca_project.sql_in|PASS|Time: 13731 milliseconds
TEST CASE RESULT|Module: pca|pca.sql_in|PASS|Time: 23499 milliseconds
TEST CASE RESULT|Module: validation|cross_validation.sql_in|PASS|Time: 1377 milliseconds
  • Connect to the database and check if the schema exists as shown here:
flightdata=# \dn madlib
 List of schemas
  Name  |  Owner
--------+---------
 madlib | gpadmin
(1 row)
  • Create the sample table and data set as shown below:
flightdata=# \df madlib.chi2_gof_test
                                     List of functions
 Schema |     Name      |    Result data type     |       Argument data types        | Type
--------+---------------+-------------------------+----------------------------------+------
 madlib | chi2_gof_test | madlib.chi2_test_result | bigint                           | agg
 madlib | chi2_gof_test | madlib.chi2_test_result | bigint, double precision         | agg
 madlib | chi2_gof_test | madlib.chi2_test_result | bigint, double precision, bigint | agg
(3 rows)

flightdata=# create table testing_madlib ( a bigint , b bigint );
NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Greenplum Database data distribution key for this table.
HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
CREATE TABLE
flightdata=# insert into testing_madlib values ( generate_series(1,10000),generate_series(1,10000));  
INSERT 0 10000 flightdata=# CREATE TABLE testing_madlib2 ( flightdata(# a SERIAL, flightdata(# b VARCHAR, flightdata(# c BIGINT, flightdata(# d DOUBLE PRECISION flightdata(# ); NOTICE: CREATE TABLE will create implicit sequence "chi2_test_blood_group_id_seq" for serial column "chi2_test_blood_group.id" NOTICE: Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'id' as the Greenplum Database data distribution key for this table. HINT: The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew. CREATE TABLE flightdata=# INSERT INTO testing_madlib2(b, c, d) VALUES flightdata-# ('A', 34, 12.90), flightdata-# ('B', 65, 90.45), flightdata-# ('C', 78, 67.45), flightdata-# ('D', 32, 10.16); INSERT 0 4
  • Test a MADlib function:
flightdata=# SELECT (madlib.chi2_gof_test(a, b)).* FROM testing_madlib ;
 statistic | p_value |  df  | phi | contingency_coef
-----------+---------+------+-----+------------------
         0 |       1 | 9999 |   0 |                0
(1 row)

flightdata=# SELECT (madlib.chi2_gof_test(c, d)).* FROM testing_madlib2;
    statistic     |       p_value        | df |       phi        | contingency_coef
------------------+----------------------+----+------------------+-------------------
 74.3979432356668 | 4.87681735844096e-16 |  3 | 4.31271211755627 | 0.974155148485107
(1 row)

 

Uninstall 

Note: In Pivotal HAWQ, uninstalling MADlib is not possible, as it is needed internally by the system. 

  1.  Uninstall using madpack:
[gpadmin@gpdbsne gpdbsoftwares]$ $GPHOME/madlib/bin/madpack uninstall -s madlib -p greenplum -c gpadmin@mdw:5432/flightdata
madpack.py : INFO : Detected Greenplum DB version 4.3ORCA.
madpack.py : INFO : *** Uninstalling MADlib ***
madpack.py : INFO : ***********************************************************************************
madpack.py : INFO : * Schema MADLIB and all database objects depending on it will be dropped!
madpack.py : INFO : ***********************************************************************************
madpack.py : INFO : Would you like to continue? [Y/N]
>>> y
madpack.py : INFO : Schema MADLIB (and all dependent objects) has been dropped.
madpack.py : INFO : MADlib uninstalled successfully.

Or you can drop the MADlib schema from the database manually:

flightdata=# drop schema madlib cascade;
NOTICE:  drop cascades to function madlib.cv_logregr_accuracy(character varying,character varying,character varying,character varying,character varying)
NOTICE:  drop cascades to function madlib.logregr_accuracy(double precision[],double precision[],boolean)
NOTICE:  drop cascades to function madlib.cv_logregr_predict(character varying,character varying,character varying,character varying,character varying)
[....]
[....]
NOTICE:  drop cascades to function madlib.array_mult(anyarray,anyarray)
NOTICE:  drop cascades to function madlib.array_sub(anyarray,anyarray)
NOTICE:  drop cascades to function madlib.array_add(anyarray,anyarray)
NOTICE:  drop cascades to table madlib.migrationhistory
NOTICE:  drop cascades to default for table madlib.migrationhistory column id
DROP SCHEMA

   2. Using gppkg, remove the MADlib rpm.

[gpadmin@mdw tmp]$ gppkg -q --all
20150419:07:46:57:016428 gppkg:mdw:gpadmin-[INFO]:-Starting gppkg with args: -q --all
madlib-ossv1.7_pv1.9.2_gpdb4.3
[gpadmin@mdw tmp]$	

[gpadmin@mdw tmp]$ gppkg -r madlib-ossv1.7_pv1.9.2_gpdb4.3
20150419:07:47:17:017215 gppkg:mdw:gpadmin-[INFO]:-Starting gppkg with args: -r madlib-ossv1.7_pv1.9.2_gpdb4.3
20150419:07:47:17:017215 gppkg:mdw:gpadmin-[INFO]:-Uninstalling package madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg
20150419:07:47:17:017215 gppkg:mdw:gpadmin-[INFO]:-Validating rpm uninstallation cmdStr='rpm --test -e madlib-1.7-1 --dbpath /usr/local/greenplum-db-4.3.4.0/share/packages/database'
20150419:07:47:18:017215 gppkg:mdw:gpadmin-[INFO]:-Validating rpm uninstallation cmdStr='rpm --test -e madlib-1.7-1 --dbpath /usr/local/greenplum-db-4.3.4.0/share/packages/database'
20150419:07:47:18:017215 gppkg:mdw:gpadmin-[INFO]:-Uninstalling rpms cmdStr='rpm -e madlib-1.7-1 --dbpath /usr/local/greenplum-db-4.3.4.0/share/packages/database'
20150419:07:47:18:017215 gppkg:mdw:gpadmin-[INFO]:-Completed local uninstallation of madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg.
20150419:07:47:18:017215 gppkg:mdw:gpadmin-[INFO]:-madlib-ossv1.7_pv1.9.2_gpdb4.3-rhel5-x86_64.gppkg successfully uninstalled.

   3. Verify using the commands shown below:

[gpadmin@mdw tmp]$ gppkg -q --all
20150419:07:47:27:017622 gppkg:mdw:gpadmin-[INFO]:-Starting gppkg with args: -q --all

[gpadmin@mdw tmp]$ psql flightdata=# \dn madlib List of schemas Name | Owner ------+------- (0 rows)

gppkg, remove the MADlib rpm.



This should resolve your requirements. 

 

Additional Articles:

1) How to upgrade MADlib : https://support.pivotal.io/hc/en-us/articles/218339117-How-to-upgrade-MADlib

Comments

  • Avatar
    Doug Little

    above test cases work, but tried to validate installation using cmd
    $GPHOME/madlib/bin/madpack -p greenplum -c gpadmin@mdw:5432/dbname install-check

    and it's failing with error
    madpack.py : ERROR: Failed executing /tmp/madlib.fRe4Vv/bayes/test/bayes.sql_in.tmp
    madpack.py : ERROR: Check the log at /tmp/madlib.fRe4Vv/test/bayes.sql_in.log

    in the log file is error
    psql:/tmp/madlib.rFe4Vv/bayes/test/bayes.sql_in.tmp:261 ERROR: plpy.SPIError: permission denifed to create temporary tables in database "database" (plpython.c:4648)

    using package 1.5

    will open case, but wanted to alert others running in to same issue.

  • Avatar
    Faisal Ali

    Thanks Doug for the feedback , sorry for the late reply.

    It seems to me in your case the database where you have installed the madlib has some sort of permission issue as indicated by the below error message

    IError: permission denifed to create temporary tables in database "database" (plpython.c:4648)
    

    I ran the check again on my 4.3.4.0 environment and it came out cleanly , would recommend to open up a case with Pivotal if you are still facing issues.

    [gpadmin@mdw tmp]$ $GPHOME/madlib/bin/madpack install-check -p greenplum -c gpadmin@mdw:5432/flightdata
    madpack.py : INFO : Detected Greenplum DB version 4.3.
    TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 274 milliseconds
    TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 2261 milliseconds
    TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 6847 milliseconds
    TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 2463 milliseconds
    TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 3544 milliseconds
    TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 2702 milliseconds
    TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 2432 milliseconds
    TEST CASE RESULT|Module: elastic_net|elastic_net_install_check.sql_in|PASS|Time: 11711 milliseconds
    TEST CASE RESULT|Module: linalg|svd.sql_in|PASS|Time: 8400 milliseconds
    TEST CASE RESULT|Module: linalg|matrix_op.sql_in|PASS|Time: 4270 milliseconds
    TEST CASE RESULT|Module: linalg|linalg.sql_in|PASS|Time: 219 milliseconds
    TEST CASE RESULT|Module: pmml|table_to_pmml.sql_in|PASS|Time: 6289 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_rf.sql_in|PASS|Time: 3324 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_ordinal.sql_in|PASS|Time: 2117 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_multinom.sql_in|PASS|Time: 2308 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_glm_poisson.sql_in|PASS|Time: 1279 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_glm_normal.sql_in|PASS|Time: 1329 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_glm_ig.sql_in|PASS|Time: 1361 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_glm_gamma.sql_in|PASS|Time: 4076 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_glm_binomial.sql_in|PASS|Time: 1725 milliseconds
    TEST CASE RESULT|Module: pmml|pmml_dt.sql_in|PASS|Time: 1747 milliseconds
    TEST CASE RESULT|Module: prob|prob.sql_in|PASS|Time: 948 milliseconds
    TEST CASE RESULT|Module: quantile|quantile.sql_in|PASS|Time: 86 milliseconds
    TEST CASE RESULT|Module: sketch|support.sql_in|PASS|Time: 78 milliseconds
    TEST CASE RESULT|Module: sketch|mfv.sql_in|PASS|Time: 199 milliseconds
    TEST CASE RESULT|Module: sketch|fm.sql_in|PASS|Time: 2293 milliseconds
    TEST CASE RESULT|Module: sketch|cm.sql_in|PASS|Time: 14944 milliseconds
    TEST CASE RESULT|Module: svd_mf|svdmf.sql_in|PASS|Time: 55109 milliseconds
    TEST CASE RESULT|Module: tsa|arima_train.sql_in|PASS|Time: 3984 milliseconds
    TEST CASE RESULT|Module: tsa|arima.sql_in|PASS|Time: 4291 milliseconds
    TEST CASE RESULT|Module: conjugate_gradient|conj_grad.sql_in|PASS|Time: 364 milliseconds
    TEST CASE RESULT|Module: data_profile|data_profile.sql_in|PASS|Time: 202 milliseconds
    TEST CASE RESULT|Module: lda|lda.sql_in|PASS|Time: 1957 milliseconds
    TEST CASE RESULT|Module: stats|wsr_test.sql_in|PASS|Time: 506 milliseconds
    TEST CASE RESULT|Module: stats|t_test.sql_in|PASS|Time: 787 milliseconds
    TEST CASE RESULT|Module: stats|robust_and_clustered_variance_coxph.sql_in|PASS|Time: 1771 milliseconds
    TEST CASE RESULT|Module: stats|mw_test.sql_in|PASS|Time: 467 milliseconds
    TEST CASE RESULT|Module: stats|ks_test.sql_in|PASS|Time: 480 milliseconds
    TEST CASE RESULT|Module: stats|f_test.sql_in|PASS|Time: 610 milliseconds
    TEST CASE RESULT|Module: stats|cox_prop_hazards.sql_in|PASS|Time: 3792 milliseconds
    TEST CASE RESULT|Module: stats|correlation.sql_in|PASS|Time: 1007 milliseconds
    TEST CASE RESULT|Module: stats|chi2_test.sql_in|PASS|Time: 1040 milliseconds
    TEST CASE RESULT|Module: stats|anova_test.sql_in|PASS|Time: 465 milliseconds
    TEST CASE RESULT|Module: svec_util|svec_test.sql_in|PASS|Time: 2818 milliseconds
    TEST CASE RESULT|Module: svec_util|gp_sfv_sort_order.sql_in|PASS|Time: 230 milliseconds
    TEST CASE RESULT|Module: assoc_rules|assoc_rules.sql_in|PASS|Time: 1200 milliseconds
    TEST CASE RESULT|Module: cart|rf_test.sql_in|PASS|Time: 27789 milliseconds
    TEST CASE RESULT|Module: cart|dt_utility_test.sql_in|PASS|Time: 81 milliseconds
    TEST CASE RESULT|Module: cart|dt_test.sql_in|PASS|Time: 21674 milliseconds
    TEST CASE RESULT|Module: convex|lmf.sql_in|PASS|Time: 2816 milliseconds
    TEST CASE RESULT|Module: glm|poisson.sql_in|PASS|Time: 2242 milliseconds
    TEST CASE RESULT|Module: glm|ordinal.sql_in|PASS|Time: 1789 milliseconds
    TEST CASE RESULT|Module: glm|multinom.sql_in|PASS|Time: 1682 milliseconds
    TEST CASE RESULT|Module: glm|inverse_gaussian.sql_in|PASS|Time: 2120 milliseconds
    TEST CASE RESULT|Module: glm|gaussian.sql_in|PASS|Time: 2037 milliseconds
    TEST CASE RESULT|Module: glm|gamma.sql_in|PASS|Time: 6057 milliseconds
    TEST CASE RESULT|Module: glm|binomial.sql_in|PASS|Time: 2944 milliseconds
    TEST CASE RESULT|Module: kernel_machines|online_sv.sql_in|PASS|Time: 2994 milliseconds
    TEST CASE RESULT|Module: kernel_machines|lsvm.sql_in|PASS|Time: 6488 milliseconds
    TEST CASE RESULT|Module: linear_systems|sparse_linear_sytems.sql_in|PASS|Time: 1149 milliseconds
    TEST CASE RESULT|Module: linear_systems|dense_linear_sytems.sql_in|PASS|Time: 769 milliseconds
    TEST CASE RESULT|Module: recursive_partitioning|random_forest.sql_in|PASS|Time: 17834 milliseconds
    TEST CASE RESULT|Module: recursive_partitioning|decision_tree.sql_in|PASS|Time: 13720 milliseconds
    TEST CASE RESULT|Module: regress|robust.sql_in|PASS|Time: 4832 milliseconds
    TEST CASE RESULT|Module: regress|multilogistic.sql_in|PASS|Time: 2244 milliseconds
    TEST CASE RESULT|Module: regress|marginal.sql_in|PASS|Time: 6696 milliseconds
    TEST CASE RESULT|Module: regress|logistic.sql_in|PASS|Time: 7904 milliseconds
    TEST CASE RESULT|Module: regress|linear.sql_in|PASS|Time: 1057 milliseconds
    TEST CASE RESULT|Module: regress|clustered.sql_in|PASS|Time: 5046 milliseconds
    TEST CASE RESULT|Module: sample|sample.sql_in|PASS|Time: 382 milliseconds
    TEST CASE RESULT|Module: summary|summary.sql_in|PASS|Time: 1531 milliseconds
    TEST CASE RESULT|Module: kmeans|kmeans.sql_in|PASS|Time: 5192 milliseconds
    TEST CASE RESULT|Module: pca|pca_project.sql_in|PASS|Time: 13731 milliseconds
    TEST CASE RESULT|Module: pca|pca.sql_in|PASS|Time: 23499 milliseconds
    TEST CASE RESULT|Module: validation|cross_validation.sql_in|PASS|Time: 1377 milliseconds
    
  • Avatar
    Jeffrey Sdoeung

    If you are upgrading or installing MADlib 1.9.1, please make sure to install the patch after installing MADlib using gppkg -i and before installing MADlib into the database using the $GPHOME/madlib/bin/madpack install command.

Powered by Zendesk