MemSQL 5.8 brings support for SAML 2.0 authentication, security audit logging capabilities, manageability enhancements, and other improvements.
A number of security enhancements have been added in MemSQL 5.8.
Users can now authenticate to MemSQL by using SAML 2.0 third-party authentication. When properly configured, a MemSQL cluster can now receive and validate SAML 2.0 assertions about a user during authentication with the database. For more information, see the SAML Authentication documentation.
MemSQL now provides audit logging capability that records all database activity and writes log files to a external location. Numerous logging levels are provided to allow system administrators to adjust both the verbosity and types of queries that can be logged. For more information, see the Audit Logging documentation.
As of the time of this publication, audit logging feature is made available and licensed only as part of the MemSQL Advanced Security Option. Before using or implementing this functionality, please consult with your enterprise's licensing administrator to confirm that your enterprise has purchased the necessary Advanced Security Option license from MemSQL.
MemSQL Ops now supports inter-agent authentication using unique API tokens. When the primary agent generates a new token, agents on other hosts can follow the primary agent by specifying its unique API token. For more information, see the following topics in the documentation:
MemSQL 5.8 introduces a new set of management views to help diagnose performance problems. These views allow you to determine where queries and system tasks are spending time, what resources are being consumed, and where bottlenecks may exist in the cluster. For more information, see the following topics in the documentation:
MemSQL Streamliner will be deprecated in MemSQL 6.0. For current Streamliner users, we recommend migrating to MemSQL Pipelines instead. MemSQL Pipelines provides increased stability, improved ingest performance, and exactly-once semantics. For more information about Pipelines, see the MemSQL Pipelines documentation.
To upgrade to MemSQL 6.0, you must first remove each of your Streamliner pipelines, and then uninstall the Spark Cluster co-located with your MemSQL cluster. Once each of the pipelines has been removed, simply run
memsql-ops spark-uninstall to uninstall the Spark Cluster.
Yes, MemSQL supports Spark integration via the MemSQL Spark Connector. The connector allows you to leverage your existing Spark clusters to write data directly to MemSQL via a performant and easy-to-use API. For more information on the MemSQL Spark Connector, please see the MemSQL Spark 2.0 Connector GitHub page.
For more information on Pipelines, please see:
- Fixed an issue where recovering reference databases could be reattached to the cluster either automatically or explicitly via
- Fixed an issue with
SHOW LOAD ERRORSwhere CSV parse errors would not be reported if
FIELDS ENCLOSED BYwas specified when executing
LOAD DATA SKIP ERRORS.
- Fixed an issue with S3 Pipelines where a pipeline would become unresponsive if a corrupt zip file was loaded.
- Due to the new Workload Profiling functionality,
distributed_plancache_summaryhave been removed.
The changelog below contains MemSQL improvements and bug fixes introduced in maintenance or revision releases. For a similar list for MemSQL Ops, see MemSQL Ops Releases.
- The following built-in functions have been added for working with vectors with 32-bit floating-point numbers:
- Fixed an issue where reference tables could be dropped under rare circumstances.
- Fixed a possible crash when querying
- Memory overhead per database has been reduced by up to 30%, depending on whether or not the cluster's
transaction_buffersystem variable has been set to a low value. For more information, see Configuring Durability.
- Performance has been improved for the
CAST()function when executed on a
- Improved support for
POLYGONtypes with a large number of vertices.
- Kerberos Authentication now supports regular expressions when granting access to a Kerberos identity. For more information, see Granting a User Kerberos Authentication Permissions.
- Memory overhead of empty tables has been reduced by as much as 40%.
- Memory usage metrics exposed in management views is now more accurate.