usage: madpack [-h] [-c CONNSTR] [-s SCHEMA] [-p PLATFORM] [-v] [-l] [-d TMPDIR] [-t TESTCASE] COMMAND MADlib package manager (1.16) positional arguments: COMMAND One of the following options: install : load MADlib into DB upgrade : upgrade MADlib uninstall : uninstall MADlib from DB reinstall : perform uninstall and install version : compare and print MADlib version (binaries vs database objects) install-check : quick test of installed modules dev-check : more detailed test of installed modules unit-test : unit tests of installed modules optional arguments: -h, --help show this help message and exit -c CONNSTR, --conn CONNSTR Connection string of the following syntax: [user[/password]@][host][:port][/database] If not provided default values will be derived for PostgreSQL and Greenplum: - user: PGUSER or USER env variable or OS username - pass: PGPASSWORD env variable or runtime prompt - host: PGHOST env variable or 'localhost' - port: PGPORT env variable or '5432' - db: PGDATABASE env variable or OS username -s SCHEMA, --schema SCHEMA Target schema for the database objects. -p PLATFORM, --platform PLATFORM Target database platform, current choices: ['greenplum', 'postgres'] -v, --verbose Verbose mode. -l, --keeplogs Do not remove installation log files. -d TMPDIR, --tmpdir TMPDIR Temporary directory location for installation log files. -t TESTCASE, --testcase TESTCASE Module names to test, comma separated. Applies to install-check, dev-check and unit-test. Example: $ madpack install -s madlib -p greenplum -c gpadmin@mdw:5432/testdb This will install MADlib objects into a Greenplum database called TESTDB running on server MDW:5432. Installer will try to login as GPADMIN and will prompt for password. The target schema will be MADLIB. $ madpack dev-check This will run dev-check on all the installed modules in MADlib. Another similar, but light-weight check, is called install-check. $ madpack unit-test -t convex,recursive_partitioning/decision_tree This will run all the unit tests that are defined in the convex module, and for decision trees in the recursive partitioning module. The -t option runs tests only for required modules, and can be used similarly for install-check, dev-check and unit-test.