Release date: 23 August 2016
MariaDB ColumnStore 1.0.2 is an alpha release of MariaDB ColumnStore. This is the second alpha release of MariaDB ColumnStore with improvements over previous alpha release of 1.0.1.
MariaDB ColumnStore 1.0.2 is an Alpha release.
Do not use alpha releases on production systems!
MariaDB ColumnStore 1.0.2 is an Alpha release. This is the second alpha release of MariaDB ColumnStore with improvements over previous alpha release of 1.0.1.
Please provide feedback in JIRA for anything that is not working as expected so that we can fix it before we make the release available for the larger community. For general "how to questions" ask questions here or subscribe to firstname.lastname@example.org
- MCOL-70: systemd service support
- MCOL-4 Build for CentOS 7
- MCOL-5 Build for Ubuntu 16.04
- MCOL-58 Non-root installs now works for columnstore mysql code
Bugs and Issues Fixed
Below is list of some of the bugs and issues fixed. For the complete list please see here
- MCOL-35, MCOL-66, MCOL-14: Concurrent DML and DDL failed
- MCOL-140: Concurrent Insert threads generate errors
- MCOL-254: ColumnStore is limited to two columns in a GROUP BY statement
- MCOL-67: config.log and possibly other autoconf artifacts are in source control
- MCOL-69: autotools based build process does not work
- MCOL-151: Columnstore engine not available after reboot
- MCOL-39: console command "getSystemConfig" return API for some parameter names
- MCOL-59: name change of Calpont.xml files
- MCOL-71: Problem changing the MariaDB release version in Columnstore build
- MCOL-113: install_calpont_mysql.sh returns function not found errors on a new installation
- MCOL-138: postConfigure mentions MySQL
- MCOL-139: MariaDB ColumnStore version confusion
- MCOL-146: build enterprise rpms from new build processes
- MCOL-68: Makefile.in missing in oamapps/mcsadmin/
- MCOL-64: Internal error: CAL0009: Error in dropping table from systables
With the fixing of MCOL-59, the MariaDB Columnstore Platform Configuration file name has changed between 1.0.1 and 1.0.2. So if you have a 1.0.0 or 1.0.1 system and you want to upgrade to 1.0.2, you will need to do the following as part of the upgrade process. If you decide to reinstall 1.0.2 from scratch, this is isn’t required.
For details on how to execute the workaround please see https://mariadb.com/kb/en/mariadb/upgrading-mariadb-columnstore-from-101-to-102/
Known Issues and Limitations
There are a number bugs and known limitations within this early Alpha version of MariaDB ColumnStore, the most serious of these are listed below. These are expected to be fixed way before the Beta release. There are some known security issues. They are listed here
- MCOL-82: Subquery using IN with VIEW returns incorrect results. Queries selecting from view and using IN in where clause with a subquery on another view returns incorrect results.
- MCOL-37: Following three window functions do not return correct value
- MCOL-75 and MCOL-74: NTH_VALUE and LAST_VALUE functions return syntax errors.
- MCOL-73): Wide table formatted display causes frontend to return error
- MariaDB ColumnStore supports wide tables storage
- Displaying the query results on a large number of columns without formatting the column works
- Displaying the query results on a large number of columns with formatting causes error at MariaDB Server level
- MCOL-45 : CREATE PROCEDURE fails.
- Do not use stored procedure with this Alpha version MCOL-16: LOAD DATA INFILE into datetime columns, data got saturated.
- Do not use LOAD DATA INFILE when importing data into datetime columns
- Use cpimport to bulk load data into MariaDB Columnstore instead. cpimports works correctly for datetime columns as well.
- INSERT INTO works for datetime columns
- MCOL-49: Drop table does not work if the PM node runs out of space.
- MCOL-259: After starting MariaDB ColumnStore Service, if queries start within few nano-seconds, queries fail with “At least one DBRoot required for that query is offline“ message
- Wait for 1 minute after the service is started, before starting to send queries
- MCOL-271 and MCOL-171: empty string and date/datetime values are treated as NULL. This means you cannot insert empty values into a NOT NULL column.
- MCOL-256: Queries that have inline comments will produce erroneous results
- While Millisecond and Microsecond storage is supported for datetime, time and timestamp columns, at this time the query results cannot return millisecond and microseconds.
- UTF-8 Limitation
- UTF-8 must be declared at the table level if the instance has been set up with a UTF-8 profile. Tables created with a non-matching character set will yield indeterminate results.
- Viewing SQL output should be done using client software that supports UTF-8 character sets.
- UTF-8 characters are not supported in object names.
RPM and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.0.2 Alpha version.
- The supported OS for this Alpha version are CentOS 6, CentOS 7 and Ubuntu 16.0.4.
- Packages can be downloaded here
The source code of MariaDB ColumnStore is tagged at GitHub with a tag, which is identical with the version of MariaDB ColumnStore. For instance, the tag of version X.Y.Z of MariaDB ColumnStore is columnstore-X.Y.Z. Further, master always refers to the latest released non-beta version. The source code is available at these locations