database/mariadb-columnstore-engine
1
0
Fork 0
mirror of https://github.com/mariadb-corporation/mariadb-columnstore-engine.git synced 2025-12-24 14:20:59 +03:00
Code Activity

MCOL-101

Browse Source
This commit is contained in:
david hill
2016-06-02 19:14:56 -05:00
parent 1a673e30c5
commit e6565f6f01
4 changed files with 27 additions and 504 deletions
Download Patch File Download Diff File Expand all files Collapse all files

313
INSTALL
View File

@@ -1,306 +1,11 @@
Installation Instructions
*************************
This is MariaDB ColumnStore 1.0.0
MariaDB ColumnStore 1.0.0 is the development version of MariaDB ColumnStore.
It is built by porting InfiniDB 4.6.2 on MariaDB 10.1.10 and adding entirely
new features not found anywhere else.
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
Copyright (C) 2014 InfiniDB, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
InfiniDB, Inc. also gives unlimited permission to copy, distribute and
modify it.
Basic Installation from source
==============================
**** InfiniDB source build instructions ****
Consult the generic installation instructions
that follow for detailed information. The short version is:
cd $HOME
git clone http://github.com/infinidb/mysql
git clone http://github.com/infinidb/infinidb
-- or --
tar -zxf <srcfile>
cd mysql
./configure --prefix=$HOME
make
make install
cd ../infinidb
./configure --prefix=$HOME
make
make install
This will create a directory called Calpont in $HOME which conatins
all the software you need.
Install the InfiniDB software into /usr/local (for example) by copying
the entire Calpont directory tree there.
After untaring the sofware or installing the RPM's, setup the software
to run (this script needs to run with root privileges). Check the Installation
Guide for addition details on using postConfigure:
/usr/local/mariadb/columnstore/bin/postConfigure
Setup some aliases:
. /usr/local/mariadb/columnstore/bin/columnsoreAlias
Connect to MySQL:
idbmysql
A suggested test scenario:
create database calpont;
use calpont;
create table caltest (col1 int, col2 int) engine=infinidb;
show create table caltest;
set autocommit=0;
insert into caltest values (1, 2);
insert into caltest values (3, 4);
commit;
select * from caltest;
To use bulk load:
1. A delimited import file should be created to match the table that
you want to import data to similar to the following. In this
example, the file will be saved as idbtest.tbl:
100|1001|
200|2002|
2. Save/place this file in a directory.
3. From that same directory, import the rows:
/usr/local/mariadb/columnstore/bin/cpimport calpont caltest caltest.tbl
And check the import:
calpontmysql calpont
select * from caltest;
That's it. Enjoy.
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:
/bin/bash ./configure CONFIG_SHELL=/bin/bash
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.
`configure' Invocation
======================
`configure' recognizes the following options to control how it operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
MariaDB ColumnStore 1.0.0 is an Alpha release. This is the first MariaDB
ColumnStore release, not all features planned for the MariaDB ColumnStore 1.0
series are included in this release.
Additional features will be pushed in future releases.
Do not use alpha releases on production systems.

BIN
InfiniDBContributorAgreement.pdf
View File

Binary file not shown.

151
README
View File

@@ -1,145 +1,12 @@
To build the software from source, consult the file INSTALL.
This is MariaDB ColumnStore 1.0.0
MariaDB ColumnStore 1.0.0 is the development version of MariaDB ColumnStore.
It is built by porting InfiniDB 4.6.2 on MariaDB 10.1.10 and adding entirely
new features not found anywhere else.
Brief Install Instructions:
MariaDB ColumnStore 1.0.0 is an Alpha release. This is the first MariaDB
ColumnStore release, not all features planned for the MariaDB ColumnStore 1.0
series are included in this release.
1. Install the 3 MariaDB Columnstore RPMs.
2. Install and start the software, run: /usr/local/mariadb/columnstore/bin/postConfigure
3. Setup some aliases: . /usr/local/mariadb/columnstore/bin/MariaDB ColumnstoreAlias
4. Connect to MySQL: idbmysql
5. Try the test in step 12 below
Detailed Installation Instructions:
1. Download the package MariaDB Columnstore-2.2.0-2.x86_64.rpm.tar.gz (RHEL5 64-BIT)
to the server where you are installing MariaDB Columnstore.
2. Obtain root user access.
3. Unpack the tarball, which will generate 4 RPMs.
tar xvf MariaDB Columnstore-2.2.0-2.x86_64.rpm.tar.gz
4. Install the 3 RPMs in this order, the MariaDB Columnstore software will be installed in
/usr/local/mariadb/columnstore.
rpm -ivh infinidb-libs-2.2.0-2.x86_64.rpm
rpm -ivh infinidb-platform-2.2.0-2.x86_64.rpm
rpm -ivh infinidb-mysql-2.2.0-2.x86_64.rpm
rpm -ivh infinidb-storage-engine-2.2.0-2.x86_64.rpm
5a.To configure and run on a single server system utilizing local disk storage,
run install script:
/usr/local/mariadb/columnstore/bin/postConfigure
5b.To configure and run on a multi-server system and/or to utilize a SAN storage
system, follow the instructions in the MariaDB Columnstore Installation Guide.
/usr/local/mariadb/columnstore/bin/postConfigure
6. Ports utilized by the MariaDB Columnstore Software
The MariaDB Columnstore MySQL daemon utilizes port 3306. To use a different port, update
the 2 locations in the following file:
/usr/local/mariadb/columnstore/mysql/my.cnf
port = 3306
port = 3306
You must reserve the following ports to run the MariaDB Columnstore Software:
8600 - 8622, 8700, and 8800
7. Setup some aliases:
. /usr/local/mariadb/columnstore/bin/MariaDB ColumnstoreAlias
8. To manually start and stop the MariaDB Columnstore Software as the root user run:
cc startSystem
To stop the MariaDB Columnstore Software, run:
cc stopSystem
9. To start/stop the MariaDB Columnstore Software during system boot/shutdown use the
chkconfig command
/sbin/chkconfig --add columnstore
/sbin/chkconfig columnstore on
10. After the MariaDB Columnstore Software has been started, use the following command to
connect to the MariaDB Columnstore OAM Console and watch for the System to go to the
ACTIVE status. The follow will repeatedly run the OAM command getsysteminfo
every 5 seconds.
MariaDB ColumnstoreOAMconsole getsysteminfo -r
Here is an example display from a Single Server Install:
System and Module statuses
Component Status Last Status Change
------------ ---------------------- ------------------------
System ACTIVE Mon Apr 6 18:07:14 2009
Module dm1 ACTIVE Mon Apr 6 18:07:12 2009
MariaDB Columnstore Process statuses
Process Module Status Last Status Change Process ID
------------------ ------ ------------ ------------------------ ----------
ProcessMonitor dm1 ACTIVE Mon Apr 6 18:06:41 2009 12753
ProcessManager dm1 ACTIVE Mon Apr 6 18:06:46 2009 12954
SNMPTrapDaemon dm1 ACTIVE Mon Apr 6 18:06:41 2009 12963
SNMPAgent dm1 ACTIVE Mon Apr 6 18:06:50 2009 13565
ServerMonitor dm1 ACTIVE Mon Apr 6 18:06:55 2009 13635
DBRMWorkerNode dm1 ACTIVE Mon Apr 6 18:06:51 2009 13640
DBRMControllerNode dm1 ACTIVE Mon Apr 6 18:06:52 2009 13645
ExeMgr dm1 ACTIVE Mon Apr 6 18:07:05 2009 14578
PrimProc dm1 ACTIVE Mon Apr 6 18:07:03 2009 13842
DDLProc dm1 ACTIVE Mon Apr 6 18:07:10 2009 14936
DMLProc dm1 ACTIVE Mon Apr 6 18:07:13 2009 15114
Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0
Once the System status is ACTIVE, enter the following to exit back to the
UNIX prompt:
CNTR<C>
Or to get back MariaDB Columnstore OAM Console Prompt,enter the following:
CNTR<D>
11. Use the following command to access the MariaDB Columnstore MySQL console:
idbmysql
Example output:
Welcome to the Mysql monitor. Commands end with ; or \g.
Your Mysql connection id is 1
Server version: 5.1.26-MariaDB Columnstore-log Source distribution
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql>
12. Run the following upgrade script to create calponsys schema and upgrade the syscolumn table: /usr/local/mariadb/columnstore/bin/upgrade-infinidb.sh
13. As an example to get you started, try this:
create database MariaDB Columnstore;
use MariaDB Columnstore;
create table caltest (col1 int, col2 int) engine=infinidb;
show create table caltest;
insert into caltest values (1, 2);
insert into caltest values (3, 4);
commit;
select * from caltest;
14. Consult the Admin Guide and Syntax Guide for additional information on how
to get started.
Additional features will be pushed in future releases.
Do not use alpha releases on production systems.

67
README.md
View File

@@ -1,60 +1,11 @@
# This is InfiniDB 4.6.2
This is MariaDB ColumnStore 1.0.0
MariaDB ColumnStore 1.0.0 is the development version of MariaDB ColumnStore.
It is built by porting InfiniDB 4.6.2 on MariaDB 10.1.10 and adding entirely
new features not found anywhere else.
## Build prerequisites
To build InfiniDB from source you will need:
* a CentOS/RHEL 5/6, debian 6/7 or Ubuntu 12/14 linux host configured for software development
Along with a working C++ compiler and GNU software development tools you will need the following extra packages:
* expect
* zlib-devel
* ncurses-devel
* libxml2-devel
* readline-devel
## Build steps
### Build environment
mkdir infinidb-src
cd infinidb-src
### InfiniDB MySQL
wget -Omysql-4.6.2-1.tar.gz https://github.com/infinidb/mysql/archive/4.6.2-1.tar.gz
tar -zxf mysql-4.6.2-1.tar.gz
ln -s mysql-4.6.2-1 mysql
cd mysql
./configure --prefix=$HOME/infinidb/mysql
make
make install
### InfiniDB
cd ..
wget -Oinfinidb-4.6.2-1.tar.gz https://github.com/infinidb/infinidb/archive/4.6.2-1.tar.gz
tar -zxf infinidb-4.6.2-1.tar.gz
ln -s infinidb-4.6.2-1 infinidb
cd infinidb
./configure --prefix=$HOME/infinidb
make
make install
This will leave you with `$HOME/infinidb` as a binary tree. Follow the Binary Download
instructions in the InfiniDB 4.6 Installation Guide (available on http://www.infinidb.co/).
## How to Contribute
* You may submit your contributions via GitHub pull requests.
* The submission must be by the original author.
* Along with any pull requests, please state that the contribution is your original work
and that you license the work to the project under the project's open source license
and the InfiniDB Contributor Agreement
(see InfiniDBContributorAgreement.pdf). Whether or not you state this explicitly,
by submitting any copyrighted material via pull request, email, or other means you agree to
license the material under the project's open source license and warrant that you have the
legal authority to do so.
* The InfiniDB Project committee will review your pull request and shall decide when and
whether to merge your request in the main InfiniDB project. The InfiniDB Project
committee will inform you of any decision regarding your request.
MariaDB ColumnStore 1.0.0 is an Alpha release. This is the first MariaDB
ColumnStore release, not all features planned for the MariaDB ColumnStore 1.0
series are included in this release.
Additional features will be pushed in future releases.
Do not use alpha releases on production systems.