commit | 81a98b229b712ff77819c694bf5b22be50ffecc8 | [log] [tgz] |
---|---|---|
author | Domino Valdano <dvaldano@vmware.com> | Wed Jul 01 18:03:54 2020 -0700 |
committer | Domino Valdano <dvaldano@pivotal.io> | Tue Jul 28 14:51:26 2020 -0700 |
tree | 634a6b44aa9de6bff663fe435745063165d4a6a5 | |
parent | 868d98d6294d5e45f6e7cb3a102b636c35e3a8c3 [diff] |
Fix Boost detection, and allow more recent versions - Removes version requirement that Boost version < 1.65 - Fixes Boost detection code. Previously, we were using the wrong CMake macro (Boost_VERSION instead of Boost_MACRO_VERSION) to check against the version. Boost_VERSION has a different format for different versions, which Boost_MACRO_VERSION is the same for all versions. Also, it was allowing 1.46 even though it says 1.47 in the user error message and comments.
MADlib® is an open-source library for scalable in-database analytics. It provides data-parallel implementations of mathematical, statistical and machine learning methods for structured and unstructured data.
See the project website MADlib Home for links to the latest binary and source packages.
We appreciate all forms of project contributions to MADlib including bug reports, providing help to new users, documentation, or code patches. Please refer to Contribution Guidelines for instructions.
For more installation and contribution guides, please refer to the MADlib Wiki.
Compiling from source on Linux details are also on the wiki.
We provide a Docker image with necessary dependencies required to compile and test MADlib on PostgreSQL 10.5. You can view the dependency Docker file at ./tool/docker/base/Dockerfile_ubuntu16_postgres10. The image is hosted on Docker Hub at madlib/postgres_10:latest. Later we will provide a similar Docker image for Greenplum Database.
We provide a script to quickly run this docker image at ./tool/docker_start.sh, which will mount your local madlib directory, build MADlib and run install check on this Docker image. At the end, it will docker exec
as postgres user. Note that you have to run this script from inside your madlib directory, and you can specify your docker CONTAINER_NAME (default is madlib) and IMAGE_TAG (default is latest). Here is an example:
CONTAINER_NAME=my_madlib IMAGE_TAG=LaTex ./tool/docker_start.sh
Notice that this script only needs to be run once. After that, you will have a local docker container with CONTAINER_NAME running. To get access to the container, run the following command and you can keep working on it.
docker exec -it CONTAINER_NAME bash
To kill this docker container, run:
docker kill CONTAINER_NAME docker rm CONTAINER_NAME
You can also manually run those commands to do the same thing:
## 1) Pull down the `madlib/postgres_10:latest` image from docker hub: docker pull madlib/postgres_10:latest ## 2) Launch a container corresponding to the MADlib image, name it ## madlib, mounting the source code folder to the container: docker run -d -it --name madlib \ -v (path to madlib directory):/madlib/ madlib/postgres_10 # where madlib is the directory where the MADlib source code resides. ################################# * WARNING * ################################# # Please be aware that when mounting a volume as shown above, any changes you # make in the "madlib" folder inside the Docker container will be # reflected on your local disk (and vice versa). This means that deleting data # in the mounted volume from a Docker container will delete the data from your # local disk also. ############################################################################### ## 3) When the container is up, connect to it and build MADlib: docker exec -it madlib bash mkdir /madlib/build_docker cd /madlib/build_docker cmake .. make make doc make install ## 4) Install MADlib: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres install ## 5) Several other commands can now be run, such as: # Run install check, on all modules: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres install-check # Run install check, on a specific module, say svm: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres install-check -t svm # Reinstall MADlib: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres reinstall ## 6) Kill and remove containers (after exiting the container): docker kill madlib docker rm madlib
Instruction for building design pdf on Docker:
For users who wants to build design pdf, make sure you use the IMAGE_TAG=LaTex
parameter when running the script. After launching your docker container, run the following to get design.pdf
:
cd /madlib/build_docker make design_pdf cd doc/design
Detailed build instructions are available in ReadMe_Build.txt
The latest documentation of MADlib modules can be found at MADlib Docs
.
The following block-diagram gives a high-level overview of MADlib's architecture.
MADlib incorporates software from the following third-party components. Bundled with source code:
libstemmer
“small string processing language”m_widen_init
“allows compilation with recent versions of gcc with runtime dependencies from earlier versions of libstdc++”argparse 1.2.1
“provides an easy, declarative interface for creating command line tools”PyYAML 3.10
“YAML parser and emitter for Python”UseLATEX.cmake
“CMAKE commands to use the LaTeX compiler”Downloaded at build time (or supplied as build dependencies):
Boost 1.61.0 (or newer)
“provides peer-reviewed portable C++ source libraries”PyXB 1.2.6
“Python library for XML Schema Bindings”Eigen 3.2.2
“C++ template library for linear algebra”Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE
file distributed with this work for additional information regarding copyright ownership. The ASF licenses this project to You under the Apache License, Version 2.0 (the “License”); you may not use this project except in compliance with the License. You may obtain a copy of the License at LICENSE
.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
As specified in LICENSE
additional license information regarding included third-party libraries can be found inside the licenses
directory.
Changes between MADlib versions are described in the ReleaseNotes.txt
file.
MAD Skills : New Analysis Practices for Big Data (VLDB 2009)
Hybrid In-Database Inference for Declarative Information Extraction (SIGMOD 2011)
Towards a Unified Architecture for In-Database Analytics (SIGMOD 2012)
The MADlib Analytics Library or MAD Skills, the SQL (VLDB 2012)