4.6.1 - Released April 29, 2019
OmniSci release 4.6.1 contains several bug fixes.
OmniSci Core
Fixed Issues
- Fixed an issue where a grouped pointmap with multiple "SAMPLE"
measures could cause a program error.
- Fixed an issue where a JOIN on the result of an unnest operation
caused a program error.
- Fixed an issue where QueryMemoryInitializer was not passed safely
to the JOIN loop builder.
- Fixed an issue where queries retried on CPU with subqueries that
had already been executed would cause a program error.
- Removed buffer size limitations between cluster aggregator and
leaves.
- Fixed an issue where
sql_execute_df would throw an
exception when encountering a BOOL column.
- Restored SQL execute timings to std_log output.
- Fixed an issue with intermittent server program errors with
CUDA error code 201 in egl compositor.
- Improved error resolution when an error is thrown during the
build of a poly cache.
- Fixed an issue with COPY TO behavior when executing in HA mode.
4.6.0 - Released April 15, 2019
OmniSci release 4.6.0 includes several bug fixes and performance
improvements.
|
Important |
- Syscatalog/catalog separation has changed directory layout.
System catalog/system database is now called omnisci_system_catalog
and is in a separate folder in catalogs. The default database
is still named mapd, but it is a standalone database.
- The
--enable-access-priv-check flag has been
removed. Access privilege verification is now required and
enabled by default for OmniSci version 4.6.0 and higher.
|
OmniSci Core
New Features
- CTAS (CREATE TABLE AS SELECT) is now supported on distributed
installations.
| Important | In release
4.6.0, avoid using CTAS to create tables with very large
row counts (for example, in excess of 10 million rows). In such cases,
the leaf-aggregate communication via Thrift imposes size limits
(2GB), which OmniSci is working to address. |
- OmniSci supports updates on variable length columns,
specifically arrays and strings with encoding NONE.
- Added
partition='replicated' option for COPY FROM command on
geo tables [specified via option WITH (geo = 'true')].
- Further foundational improvements in efficient columnar
output, allowing for better memory efficiency with larger result
sets. This is behind a configuration flag and will be turned on
by default in a future release.
- Added support for importing from gdb(Esri geodatabase) format.
- Added support for importing from Parquet files, from both
local and S3, including auto-detect capabilities on omnisql.
Immerse will support import of Parquet files in a future release.
- Improved string dictionary performance from use of rk_hash
fingerprints. This is behind a configuration flag and will be
turned on by default in a future release.
- Added support for custom S3 endpoints, allowing for non-AWS
S3-compatible storage systems to be used as input sources.
- Added support for Single Sign-on using Okta (SAML 2.0
Identity provider) for authentication.
| Note |
There is a known limitation with users set up via Okta, where
such users cannot be Superusers. OmniSci will address this in
an upcoming release.
|
\l command to list users' database access is now
available to non-Superusers.- Added support for PKI-based authentication starting with the
ODBC API.
- Users can now be assigned a default database as part of
CREATE or ALTER USER command options.
- SQLImporter now supports HTTPS and HTTP besides the binary
protocol.
- Lifted limit on dictionary entries from 1B to 2B, allowing for
larger string dictionaries.
- Logging format now standardized to allow for better import of
OmniSci logs in a delimited file format (some minimal post-processing
is required).
- Improved performance of between 25-35% on string dictionary
reloads from better thread utilization.
- String dictionary server status now visible as part of
\status command in omnisql.
- Added support for specifying TIMESTAMP precisions, including
TIMESTAMP(3) - milliseconds, TIMESTAMP(6) - microseconds and
TIMESTAMP(9) - nanoseconds.
Immerse will support this feature in a future release.
- Added support for CARDINALITY for array columns (returns the
number of elements — for example, the length of an array column).
- Added support to allow variable length array columns to be set to NULL.
- Added early, experimental support for scalar user-defined
extension functions written in C++/CUDA. These kernels can now be
compiled on server startup and visible to the server runtime
immediately. Please refer to the relevant OmniSci documentation
for details on how to use this capability.
- Added Thrift support to list the databases that can be
accessed by the currently logged in user. Also added support
for a user, once logged in, to switch between these databases
without needing to login again.
- Added support to allow for dashboards to be shared via roles.
- Eliminated per-fragment overhead for non-lazy GPU projections,
allowing larger result sets for rendering and other use cases.
Fixed Issues
- Fixed issues with non-existent source in dashboard metadata
which was causing migration to fail - this is now logged to
enable better diagnosis of the scenario.
- Fixed an issue where an empty array query resulted in a server
program error under certain circumstances.
- Fixed an issue where the Calcite server alone failed, resulting in
an unusable but running OmniSci Server. Now, should the Calcite server
fail, OmniSci Server does not allow new connections. The failure is captured
in the logs, and OmniSci Server is stopped so that the
systemd
utility can restart both the OmniSci and Calcite servers.
- Fixed an issue where binary load from arrow load for DATE
resulted in incorrect data.
- Fixed an issue where an INTERVAL ADD to timestamp resulted
in a program error.
- Fixed a case where a large number of noisy error messages
were generated in the logs from auto-completion hint failures.
- Fixed issues with spurious and potentially confusing
"Connection refused" Thrift messages on server startup.
- Fixed an issue with inability to export a dashboard from admin
account, when admin is not the owner of the dashboard.
- Fixed an issue where OmniSci HA node goes out of sync after
program errors during execution of Kafka message instructions.
- Fixed an issue with ALTER TABLE RENAME on multipolygon columns.
- Fixed an issue where querying views with joins resulted in a
watchdog error.
- Fixed an issue where dropping a database resulted in
recycled database IDs that caused unexpected behavior in the catalog.
- Fixed program error on selecting Geo column from Outer Join.
- Fixed program error resulting from certain SELECT * queries.
- Fixed case where GRANT SELECT VIEW on database resulted in
Update privilege.
- Fixed cases where CTAS (CREATE TABLE AS SELECT) involving
SELECT *, or CASE statements resulted in a program error.
- Fixed an error related to High Availability being disabled
when LDAP was enabled.
- Fixed an error in High Availability mode related to dashboard
objects not being replicated.
- Fixed an issue with version 4.4.2 not correctly updating buffer
shapes on map unless map boundaries change.
- Fixed a rendering regression related to log/sqrt/pow scale
types in Vega.
- Fixed an issue where Optimize Table command resulted in extra
disk space being consumed on each run.
- Fixed an issue with ODBC sessions stopping on reconnect. ODBC
sessions now continue upon successful reconnect to omnisci_server.
- Fixed an issue regarding incorrect text array length
is shown in the new table after running CTAS.
- Fixed an issue where SELECT queries failed after UPDATE on a
newly added text column added via ALTER TABLE ADD COLUMN.
- Fixed an issue with visibility of s3 credentials in history
file.
- Fixed a threading issue in CTAS that caused server failure.
- Fixed an issue related to LDAP that affected omnisci_server
users who had not yet been set up in the system.
- Fixed an issue where multiple SAMPLE invocations in a single
query resulted in inconsistent results.
- Fixed an issue with program error on updating copy_params and
re-detecting CSV.
- Fixed an issue with approx_count_distinct causing system
failure on GROUP BY with more than one group.
OmniSci Render
Fixed Issues
- Fixed an issue where ST_ functions on a geo column used in a
color measure were not parsing correctly in render request.
- Fixed an issue with incorrect renders on distributed systems
involving Vega transforms with aggregate queries.
OmniSci Immerse
New Features
- Immerse supports integration with OKTA/SAML for Single
Sign-On based authentication.
- Tables can be deleted directly from Data Manager.
- Data can be added to any table via the Append functionality
in Data Manager.
- All rows within a table can be removed via the
Delete All Rows functionality in Data Manager.
- Users can denote when a file has a header row during data
import, using the Includes Header Row option within Import
Settings.
- Added in situ poly rendering for backend-rendered choropleths,
greatly enhancing performance at scale.
- Added sampling to server-rendered Choropleths.
- Added crossfiltering and bounding box filter to server-rendered
Choropleths.
- Max number of groups that can be visualized in Bar and Bubble
charts increased from 100 to 500.
Fixed Issues
- Fixed an issue where clause sampling caused overflow with
greater than 3.4 billion records.
- Fixed an issue where brush was not aligned with bin increment in
Combo chart.
- Fixed an issue where Amazon S3 import could not be performed
using a full link URL.
- Turned off ability to rotate MapBox base maps to improve
usability.
- Import Data button is hidden on Data Manager screen if user
lacks privileges to import data.
- Fixed inconsistencies with timezones; all dates shown in
Immerse are displayed as UTC.
- Fixed an issue where the OmniSci logo appears before being
overwritten by servers.json configurations.
- Fixed an issue where Choropleth pop-up does not disappear
when user zooms in on the map.
- Fixed an issue in Bar chart where sort by selection was saved
but not applied when switching color measures and aggregates.
- Fixed an issue in Stacked Bar chart where custom colors
selected in the color palette were not respected on the chart
display.
- Fixed an issue with Stacked Bar where axis label renaming was
not persisting.
- Fixed an issue in Combo chart where the chart editor right
panel would become unresponsive after certain settings were
configured.
- Fixed an issue that prevented a user from changing measure
formatting without clearing formatting first.
- Fixed an issue with incorrect default formatting.
- Fixed an issue in chart editor where popup remained active
after required measure/dimension had been selected.
- Fixed issues in Table chart, Histogram, and Heatmap that
prevented date formatter from showing up correctly.
4.5.0 - Released February 21, 2019
OmniSci release 4.5.0 includes several bug fixes and performance
improvements.
OmniSci Core
| Important |
-
With release 4.5.0 and higher, OmniSci now requires that all configuration
flags used at startup match a flag on the OmniSci server. If any flag
is misspelled or invalid, the server does not start. This change helps
to ensure that all settings are intentional and will not have unexpected
impact on performance or data integrity.
- Licenses are now required for OmniSci Enterprise Edition.
Servers start but are not functional without a valid license file
installed.
- OmniSci configuration files are now strictly validated on
startup. Servers do not start with an unrecognized option in the
configuration file, and an error message is logged to stderr
containing the unrecognized option.
- Default port numbers for OmniSci services have been changed.
In addition, the names of key services are now prefixed
with omnisci_, changing from mapd_. Symlinks from the old names are
provided, but will be removed in future versions. Please note these
changes and upgrade any scripts/workflows that use the old names.
| Service | Old | New |
|---|
| omnisci_web_server | 9092 | 6273 |
| omnisci_server tcp | 9091 | 6274 |
| omnisci_server http | 9090 | 6278 |
| calcite | 9093 | 6279 |
| omnisci_sd_server | 10301 | 6277 |
| omnisci_web_server http to https redirect | 9094 | 6280 |
- OmniSci 4.5 includes a backward-incompatible change to metadata
for DATE columns being updated. This migration is handled
automatically for the default
mapd database on server
start. Secondary databases are upgraded on first connect. Running
the OPTIMIZE command should address any issues with the metadata.
These migrations cause a one-time delay in server startup, so please
ensure you can connect to these databases at upgrade time to avoid
these delays.
- Due to a system-related change in the behavior of DROP/TRUNCATE,
data files are not deleted from disk, but
tombstoned
and identifiable by the DELETE_ME prefix on the filesystem for up to
five minutes after you issue the command.
- (Applicable to distributed installs only): StringDictionaryServer
now lazy loads
dictionaries on request. Consequently, the first request to a
dictionary-encoded column of a large table can be slow for very
large tables with high-cardinality string dictionary columns.
- The
--gpu and --cpu flags are
replaced with the --cpu-only flag for OmniSci Server.
|
New Features
-
Community Edition has been deprecated and replaced with Enterprise Trial.
See https://www.omnisci.com/platform/downloads/
for details.
-
Renamed key components from MapD to OmniSci. Specifically:
-
mapd_server is now omnisci_server.
-
mapd_web_server is now omnisci_web_server.
-
mapdql is now omnisql.
-
String Dictionary Server is now omnisci_sd_server.
-
JDBC connection strings now are jdbc:omnisci:localhost:6273:<dbname> and the
JDBC driver class changes to com.omnisci.jdbc.OmniSciDriver.
-
Better memory handling through improved estimation of query GPU memory
requirement. Allow-cpu-retry is now turned on by default, which allows
queries in certain low-GPU-memory situations to be identified and executed on
CPU automatically.
-
OmniSci Core now supports inserts of array literals containing NULLs.
-
OmniSci Core now supports importing csv files with arrays containing NULLs.
-
Changed default port from 9092 to 6273 to avoid conflicts with other well known
services running on those ports.
-
DECIMAL / NUMERIC fields can now be downcast to different scale/precision.
-
Dictionary size limit now increased to ~2.15Billion entries.
-
Deleting tables using the DROP command will immediately remove the table from
the catalog but asynchronously remove data from disk.
-
Added interval support for DATEPART/DATEADD operations.
-
DATEPART - weekday, quarterday
-
DATEADD - week, weekday, decade
-
Added ability to recompute table metadata on demand using the OPTIMIZE command.
Fixed Issues and Enhancements
- omnisci.conf is now validated at server start. This is to prevent any
erroneous configuration settings taking effect. If erroneous config parameters
are found, the server fails to start and throws an error.
-
Fixed issues when geo data is imported (for example from PostGIS) via JDBC.
-
Replaced
--gpu and --cpu flags with a --cpu-only
flag for OmniSci Server.
-
Fixed an issue where geo files could not be appended to tables created through
Immerse geo file import process.
-
Fixed program error caused by selecting SAMPLE on a geo data type column.
-
Fixed an issue with ODBC not reconnecting on a server restart.
-
Fixed certain cases where DATE was handled incorrectly by SQLImporter.
-
Fixed an issue where session IDs were being logged in certain cases.
-
Fixed an issue where Importer did not estimate number of rows correctly.
-
Fixed an issue with JDBC handling of the type of a geo column.
-
Fixed an issue where JDBC needs to filter DB information from Table Priv Call.
-
Fixed an issue that prevented sharding on a date column.
-
Fixed an issue where projecting a varlen target inside SAMPLE in distributed
mode could corrupt subsequent columns.
-
Fixed a typo in table schema output from the
\d command in omnisql.
-
Fixed an issue projecting varlen columns inside a top k query
(for example,
SELECT str, x FROM proj_top ORDER BY x DESC LIMIT 1;).
-
Resolved a program error when running a subquery projecting dictionary encoded
strings inside an
IN expression.
-
Fixed an issue where out-of-bound integer ranges fed to timestamp column
erroneously get turned into null sentinels.
-
Conditionally remove
ST_CONTAINS filter when computing the filtered count
for a geo join.
-
Improved accuracy of
ST_CONTAINS on certain complex MULTIPOLYGON shapes.
OmniSci Render
Fixed Issues and Enhancements
-
Fixed an issue with Vega Scale parse failing if range values are whole numbers.
-
Fixed an issue with GLLayoutBuffer exception related to rendering the same Vega in
two successive
render_vega calls.
-
Fixed intermittent error with renders using Percent Accumulation Scale.
-
Enhancements to messages related to Vega parse errors.
OmniSci Immerse
New Features
-
Enterprise edition trial (see
https://www.omnisci.com/platform/downloads/ for details).
- Add support for lasso filter on line map chart.
- Added clarity to formatting options and created a new option to represent
billions as B.
- Geo Heatmap colors rendered that do not fall in scheme selected now display
in grey rather than purple.
- Sort null measure values to the end by default for grouped chart queries
(crossfilter and Stacked Bar charts).
Fixed Issues and Enhancements
-
Fixed an issue with session connection being lost on timeout.
-
Fixed ability for data tables to be switched via the search interface in Data
Manager.
-
Fixed an issue where exported CSV does not match chart or omnisql data.
-
Fixed circle, polygon and lasso filters for Linemap.
-
Fixed cross-filtering for Number chart.
-
Fixed an issue with losing color when clicking on column in Stacked Bar chart.
-
Fixed an issue with overflow of bars when switching to Stacked Bar chart.
-
Fixed issues with non-functioning backend-rendered multi-layer map and
backend-rendered multi-layer Scatter Plot examples.
-
Fixed an issue where Stacked Bar chart was not maintaining a filter on dashboard load.
-
Fixed an issue with HeatMap chart related to the assignment of default green colors
for 0 values. Values that are 0 are assigned the mid-range green color.
-
Fixed an issue in Chart Editor where disabling NULL values after a dimension drag
and drop generated a query causing a 502 error.
-
Fixed an issue with Immerse failing to load correctly if there was no
servers.json file.
-
Fixed an issue with disappearing dashboard header in certain cases.
4.4.2 - Released January 9, 2019
OmniSci release 4.4.2 includes several bug fixes and
performance improvements.
OmniSci Core
Fixed Issues and Enhancements
- Improved error logging when the
mapd_server release is
older than the server's data directory.
- Added support for Arrow DATE values using small date
buffers.
OmniSci Immerse
Fixed Issues and Enhancements
- Fixed an issue where using conditional expressions
(
CASE WHEN condition THEN result ELSE default END) in a custom
SQL dimension would cause a chart error.
4.4.1 - Released January 2, 2019
OmniSci release 4.4.1 includes new features as well as
several bug fixes and performance improvements. It comprises the 4.4.0
release version and a fixed regression.
OmniSci Core
New Features
- Added support for the
ST_Disjoint, ST_DWithin, and ST_DFullyWithin geospatial functions.
- Added support for
get_session_info() Thrift API.
- DATE datatype is compressed. Dates now have two smaller encoding sizes: 4 bytes (default) and 2 bytes. Existing date columns continue to work as before.
- Added support for SAML authentication with Okta (Enterprise Edition only).
Fixed Issues and Enhancements
- Usernames can now include dashes.
- Attempting an ST_Contains join with a geospatial string literal argument no longer causes a program error.
- User session IDs are no longer potentially exposed in OmniSci Core log files.
- The hit-test cache limit has been removed and should eliminate the following error: "Cannot retrieve results for query <query>. The results have not been cached for hit-testing."
- Fixed database consistency errors that could occur if the underlying filesystem ran out of disk space.
- Fixed a synchronization issue for overflow/underflow checks on NVIDIA Volta and Turing GPUs.
- Improved performance on String Dictionary import for multiple String Dictionary-encoded columns.
- Intermediate ResultSets are now automatically compressed before being shipped between the aggregator and leaf servers. This allows ResultSets over 2 GB in uncompressed size to be passed around the cluster and can result in performance improvements due to better utilization of network bandwidth.
- Fixed an issue where concurrent updates/deletes in import operations could cause table corruption.
- Fixed a corner case where BOOL, TINYINT, or SMALLINT columns could result in invalid data during import.
- Fixed an issue with rowids projected in CTAS that caused an error in table creation, because rowid is a reserved column name.
- Added support for AM/PM designation in timestamps.
- Fixed an issue where sharded tables with geospatial columns could cause a program error during insert or projection queries.
- Improved performance for queries using 32-bit timestamps.
- Improved memory usage during hash joins.
- Fixed an issue in which hash joins on Dictionary-encoded strings, where one of the columns was empty, could cause a program error.
- Deprecated/removed the following obsolete flags:
--disable-rendering, --db-convert, fast-strcmp, and multi-subquery-exec.
OmniSci Render
New Feature
- Support is added for pct/blend accumulation rendering modes in distributed configurations.
Fixed Issues and Enhancements
- Multiple point/symbol layers using Vega projections no longer potentially render a blank image.
- In distributed configurations, a multilayer rendering issue occurred in which an aggregate query and a projection query, each referencing Vega transforms, could cause a program error. This has been fixed.
- Using Vega transforms on line/poly queries with empty data no longer causes an error; it now produces an empty image, as expected.
OmniSci Immerse
Fixed Issues and Enhancements
- Improved error tracking to allow better triage and resolution.
- Fractional numbers are now supported in global filters in Immerse.
- Fixed an error that occurred when switching chart types with binned dimensions.
- Deprecated: The Export Chart button has been removed from Text charts.
- SAMPLE aggregate is added as an option for all chart measures in conjunction with GROUP BY.
- Fixed ambiguous-column error for identically named columns on geo joins.
- Fixed issues with importing of tables with geospatial columns.
- Resolved issue with modifications to Custom Colors on Combo charts with color dimensions were reflected in the right pane of the UI, but not the chart palette, which caused incorrect rendering.
- Updated license uploading for Community Edition.
4.3.0 - Released November 19, 2018
OmniSci release 4.3.0 consists of a number of new features as well as
several bug fixes and performance improvements outlined below.
OmniSci Core
New Features
- Decimal compression: Decimals now automatically use the smallest possible encoding for the specified precision/scale.
- Hash joins now support null left-hand side joined to not null right-hand side and vice-versa.
- Hash joins allow different integer types between the left-hand side and right-hand side.
Fixed Issues
- Ensure MAX_ROWS is an integer literal and properly reject non-integer values.
- Fixed an issue where CTAS did not properly parse date_trunc functions and geometry casts.
- Fixed an issue where DROP DATABASE did not remove all table data from disk.
- Fixed an issue where the minus sign was being counted as part of decimal precision.
- Improved error handling in distributed mode.
- JDBC now properly generates boolean string literals when
setBoolean is called.
- Properly validate DECIMAL type ranges and check for overflows.
- Resolved an issue where DB owners may not have access privileges on new databases by default.
- Resolved a system failure that occured for unsupported DDL statements.
- Resolved a system failure that occured if a database were created then dropped before a user connected to it.
- Resolved a system failure that occured when serializing multiple geospatial types in distributed mode.
- Resolved a system failure when clearing GPU memory from mapdql when no GPUs are present.
- Resolved a misleading error message no dashboards were returned while listing dashboards in mapdql.
- Resolved a problem with geo append when existing table has uncompressed coords
- Resolved an issue where ALTER TABLE on a view caused a system failure.
- Resolved an issue where an invalid geospatial literal could cause a system failure.
- Resolved an issue where approx_count_distinct could send too much data and/or cause a system failure during serialization in distributed mode.
- Resolved an issue where deleted users were not totally purged after being dropped.
- Resolved an issue where hash joins on distributed would run incorrectly if one of the tables was not replicated or both tables were not sharded.
- Resolved an issue where object privilege migration could be incomplete.
- Resolved an issue where precision errors could occur during queries involving aggregates.
- Resolved an issue where session timeouts could cause a system failure in distributed mode.
- Resolved an issue where the roles display for a user could be incorrect.
- Resolved an issue where using privilege APIs could cause a system failure if object level privileges were disabled.
- Resolved precision errors in ST_Distance and ST_Intersect for some geospatial types.
- Resolved various issues in automatic FROM clause table reodering.
- The last row of a CSV file is no longer ignored if the CSV file does not have a trailing new line.
OmniSci Render
New Feature
- Added support for in-situ line rendering (i.e. without a copy) for projection queries (LINESTRING columns only)
Fixed Issues
- Properly handle rows where all columns are NULL in the Vega transforms API.
- Resolved an issue handling NULLs in Vega scales.
- Resolved an issue when multiple sessions ran the same polygon hit testing query.
- Resolved an issue where Vega projections would fail to be applied.
OmniSci Immerse
New Feature
- Enabled in-situ line rendering for linemap.
Fixed Issues and Enhancements
- Added schema validation to prevent an edge case where dashboards could become corrupt and unloadable.
- Fixed an issue with linemap hover popups on single node instances.
- Fixed an issue where decimal-baded global filters returned incorrect results.
- Fixed an issue where the Y-axis measure in the stacked bar chart could be missing a name label.
- Fixed an issue with categorical color measures in choropleth that could result in a hang.
- Fixed an issue where formatting dates on combo chart could result in a hang.
- Added code to ensure measure aggtypes can be updated on linemap.
- Removed an error thrown when changing choropleth color dimensions.
- Fixed an error in linemap where geo column names other than mapd_geo or omnisci_geo could cause errors.
- Improved handling of null data on piechart.
- Adjusted linemap hit testing behavior to match pointmap.
- Added code to prevent an issue where dashboard state was not preserved when switching to SQL Editor.
- Fixed an issue with custom SQL measures in linemap.
- Improved the legend for min/max numerical color scale for linemap.
- Optimized viewport clipping for rectangular/non-complex shapes.
- Added code to ensure measure aggtypes can be updated on linemap.
- Improved handling of color measures for linemap.
- Improved linejoin drawing techniques for linemap.
- Prevented linemap from showing in rendering-disabled environments.
- Added code to ensure adding and deleting custom colors on combo propagates to the chart.
- Improved error logging and persistence for SQLLogger.
- Enabled in-situ line rendering for linemap.
- Fixed timezone issues for certain timestamps set to midnight (00:00:00).
4.2.0 - Released October 29, 2018
OmniSci release 4.2 consists of a number of new features as well as
several bug fixes and performance improvements outlined below.
OmniSci Core
New Features
- Added top-level ACCESS privilege to check if a user logging in has
any object permissions at all, and restrict Immerse capabilities
accordingly.
| NOTE | This is a backward incompatible
change. OmniSci recommends that you back up your existing database
before installing OmniSci 4.2. |
- Added GRANT ALL privilege on database to allow for better management of object privileges
- Added https support now available for major APIs - JDBC, Thrift, pymapd, KafkaImporter, StreamImporter APIs and mapdql
- Added ST_MaxDistance allowing users to compute the maximum distance between a POINT and a LINESTRING
- Added ST_Distance support for MULTIPOLYGONS
- Added ST_Intersects support for MULTIPOLYGONS
Fixed Issues
- Fixed an issue with simple literal additions returning incorrect results
- INSERT now works correctly with text[] column types
- SAMPLE now handled correctly on array types
- Faster imports of dictionary-encoded string data - upto 3x performance improvement, depending on the data
- OmniSci now uses LLVM 7.0
- Catalog properly loaded even if a user logs into the non-default database first
- Roles can now GRANT to other roles, rather than just individual users - this fixes an existing issue with dashboard sharing to/from roles
- get_all_roles_for_user() thrift call now works for roles as well
- OmniSci now supports Arrow 0.10.0 and 0.11.0
- db_object_privs thrift call now supports user privileges
- GRANT now supports granting multiple privileges to multiple grantees in a single command allowing for better privilege management
- has_object_privilege thrift call now supports recursively returning privileges for a given user, which identifies not just their directly granted privileges but also those granted via roles
- Projection queries now support columnar outputs, significantly improving the efficiency of memory management for query results.
- ALTER TABLE now enabled for non-super users
- Fixed incorrect timestamp precision encoding, including handling of leading zeros
- Fixed edge case issues with decimal formatting for display
- SAMPLE now supports varlen arguments in distributed mode with GROUP BY
- Fixed an issue with long-running first load queries disallowing Immerse logins
- Fixed an issue with array projections needed for improved GeoSpatial support in a distributed installation
- Improvements to geo import robustness
- GeoSpatial queries now supported properly in distributed mode
- Fixed issues with POLYGON/MULTIPOLYGON handling within ST_Intersects
- All default GeoSpatial tables now use omnisci_ as the prefix. Please update any scripts that use these tables accordingly
- The default geo column name is now omnisci_geo (from mapd_geo). Please update any scripts accordingly
- Fixed certain edge cases in ST_Contains(POLYGON, LINESTRING) that caused incorrect results
- ST_Contains extended to support ST_Contains(MULTIPOLYGON, LINESTRING)
- Several improvements in CTAS robustness - CTAS now supports most major types including GeoSpatial types (NOTE - currently these improvements are restricted to a single node. This restriction will be removed in an upcoming release)
- OmniSci now uses GDAL 2.3.2 (geo import library)
- Import reports line number of bad geo in CSV files
- Bulk inserts for geo data now supported via JDBC API
OmniSci Render
New Features
- Added support for TINYINT in vega transforms
- Added support for rendering buffers larger than 4GB
- Added distributed line-rendering support.
Fixed Issues
- Fixed an issue preventing Polygon rendering if the first render query returned empty results
- Allow line/poly rendering even if render-mem-bytes is set to zero
- Symbol sizing in vega now supports distance units (meters). Subsequent releases will integrate this into Immerse geo charts.
- Prevent renderer system failure in certain cases on shutdown via SIGINT
- Fixed an issue with switching density accumulation from max/min to stddev
- Fixed issues with apparently incorrect render memory allocation on multiple devices
- Fixed system failure caused with COPY/TRUNCATE/DROP statements executed after clear_gpu_memory is run with rendering enabled
OmniSci Immerse
New Features
- Combo and Stacked bar charts support percentage (relative) views
- Added support to show/hide SQL Editor in a configurable manner.
See Roles and Privileges for configuration information
- Added Linemap Geo Chart, allowing
for LINESTRING data to be displayed and used in Geo joins as well.
This chart type works with multi-layer geo charts
Fixed Issues
- Several improvements in performance, usability and robustness of the Stacked Bar chart
- Stacked Bar chart now supports CSV export
- Multiple improvements and fixes to chart legends on multilayer Geo charts
- Multiple improvements to Combo Chart related to data loading indicators and behavior
- Fixed minor issues with navigation icon alignment on Chart Editor
- Fixed an issue causing overrides of user-specified column names in Table Importer
- Raster charts no longer fail to render correctly if a dimension is added after omnisci_geo measure is added
- Fixed an issue with lineStyle being lost upon save/apply actions in certain cases on the Combo chart
- Fixed edge case issues with handling negative values in Combo and Stacked Bar charts
- Table importer: support for DOUBLE types and also fixed handling of TIME types
- Removed 'atlas' mapbox style (no longer valid) from servers.json
4.1.3 - Released September 27, 2018
The 4.1.3 release is primarily focused on rebranding MapD to OmniSci.
Core Fixed Issue
- Fixed an issue where Core might experience a system failure when
consuming autocomplete data.
Immerse Fixed Issue
- Fixed a performance issue applying a relative date range global
filter to a combo chart.
4.1.2 - Released September 11, 2018
| Note | Version 4.1.2 was a limited release with minor bug fixes and performance
enhancements. |
4.1.1 - Released September 4, 2018
| Note |
New users no longer have default access to client tools.
To provide new users with access to Immerse and client tools,
you need to grant them the ACCESS privilege.
See
Database Object Privileges
.
|
New Features in MapD Core
MapD Core includes the following new features.
- Added geospatial operator/function support:
ST_Within (inverse of ST_Contains).- Cartesian and Geodesic
ST_Length.
- Cartesian and Geodesic
ST_Perimeter for POLYGON and MULTIPOLYGON.
- Cartesian
ST_Area for POLYGON, MULTIPOLYGON.
See Using Geospatial Functions.
- Improved performance by reducing fixed overheads during JIT Query compilation.
- Support for both fixed and variable length arrays. See Datatypes.
Resolved Issues
The following issues are resolved in MapD 4.1.1.
MapD Core
- The name of the JDBC driver has changed and is now versioned.
It takes the form mapdjdbc-<release-number>.jar,
where <release-number> changes in sync with each
release. For example, the current JDBC driver file name is
mapdjdbc-4.1.1.jar.
- Fixed typos in description for configuration flags.
- Emails can now be used as usernames.
- JDBC now supports geometry types, timestamps on
SELECT queries.
- Fixed invalid HA configurations in certain cases, due to quotes in configuration parameters.
- Fixed system failure on fixed length array import in distributed mode.
- Fixed system failure on
ALTER/DROP table.
- Fixed an issue where duplicate
CASE statements
in WHERE filter conditions compared with an OR operator caused a segfault.
- Improved connection safety on MapD session creation.
clear_gpu and clear_cpu now work correctly in distributed mode.- mapd_server no longer becomes unresponsive when making too many connections in distributed mode.
- Improved query times for expressions with a large number of
IN operators.
- Allow configurable expiry of sessions - inactive sessions
can be expired in a configurable manner, and extremely
long running sessions can be controlled with a session
timeout.
- Fixed issues with edge case inaccuracies in
ST_Contains.
- Fixed system failure related to edge case on revoking
<username> role from <username> when
<username> logs in.
- Fixed errors with certain geo import edge cases.
- Fixed system failure on subsequent
SELECT queries after
ALTER TABLE ADD COLUMN was used to add a geo column.
- Fixed inability to append to existing geo table. Geo append
is now faster with large tables.
- Allow dashes in role names.
- Fixed an issue with distributed metadata updates.
- Fixed invalid credential in HA connection processing.
- Fixed system failure on temporary tables with geo columns.
- Rename
LAST_SAMPLE to SAMPLE. LAST_SAMPLE is deprecated.
- Fixed bug in
mapdql preventing proper handling of decimal arrays.
- Add
idle_session_duration for invalidating inactive sessions.
- Add ability to obfuscate session ID in MapD server logs.
- Fixed mapd_server system failure when using a subquery in a where clause that references a view.
- S3 import fixes:
- Fix a constraint that s3 importer could detect/import at most 999 files.
- Fixed a bug where S3 importer needed to download all
files in an archive before it could detect columns.
- Migration history now uses correct table name.
- Fixed header skipping on detection with header=true.
- Better handling of NULL values/EMPTY geometries. Rows imported
into geo tables with NULL/EMPTY geometry values in geo fields now
cause entire row to be skipped during import.
- Added
ACCESS privilege to allow or deny login access for accounts with no privileges.
Rendering
- Fixed run-time shader compile failure in Symbol shader when using packed colors.
- Fixed mapd_server system failure while trying to render extremely large polygon table.
4.1.0 - Released July 31, 2018
New Features/Improvements
The following are features and improvements in MapD 4.1.0.
Core
- Ability to synchronize user roles from LDAP (Enterprise Edition only)
- ALTER TABLE ADD COLUMN now supported.
- GRANT/REVOKE ALL ON DATABASE now supported.
- Improved performance on Nvidia Pascal and Volta architectures on single column low-cardinality GROUP BY with COUNT(*) by using GPU shared memory.
- Calcite version upgraded to 1.16.
Immerse
- Stacked Bar Chart released.
- Several performance/stability improvements on Combo chart.
- Import UI - Ability to specify tables as replicated for distributed deployments.
- Additional user interface customization options (see documentation for details).
- Added auto-zoom to data bounds on geo heatmap chart.
Resolved Issues
The following issues are resolved in MapD 4.1.0.
MapD Core
- Removed hidden physical columns from select * expansion for geospatial types.
- Fixed mapdql system failure when running `\d` on a view with geospatial columns.
MapD Core Enterprise Edition
- Fixed an issue where projecting float columns could return an incorrect value in distributed mode.
- Fixed an issue where case statement with strings caused system failure in distributed mode.
- Fixed an issue where none encoded string could system failure the aggregator in distributed mode.
- Fixed an issue where swap table order on a distributed join with one replicated table could give incorrect results.
- Fixed an issue where sharing dashboards with users but not roles did not work.
- SuperUser role from LDAP did not automatically have superuser privileges granted.
- Allow Grant privileges to a role that is corresponding to LDAP role
- Fixed a segfault issue on `LAST_SAMPLE` when serializing resultset on distributed.
- Login fails when LDAP properties are defined in mapd.conf.
- Fixes to handling of table reordering for joins in a distributed setting.
Immerse
- Removed double group-by in backend-rendered choropleth, improving performance
- Now supports text types in backend-rendered choropleth chart color measure.
- Added autozoom on creation of geo heatmap.
- Fixed an issue where column header names revert to `column_1`, `column_2` etc. upon import after changing a CSV import setting.
- Removed/suppressed additional options in 4.1 'About Immerse' dropdown.
- Fixed an issue where dashboard Save button was not showing in all cases.
- Fixed an issue where brushed range chart on the area line combo chart was unable to render a focus chart with extracted timestamps.
- Fixed an issue where auto-selecting mapd_geo ignored the dimension column for a join.
- Can now set a global filter on datasets containing arrays.
- Fixed an issue where combo chart focus and range brushes were out of sync.
- Fixed an issue on combo chart where the x-axis was misaligned when the x-axis dimension was a numeric datatype.
- Immerse now supports TINYINT datatype.
- Fixed an issue on Internet Explorer where the EULA accept button did not appear until the window was resized.
- Fixed an issue where the global filter icon was not activated for a custom measure filter.
- Fixed an issue where switching from Choropleth to Geo Heatmap threw an error and the Geo Join component was not clearing.
- Fixed an issue where the dimension was not applied to Scatter/Pointmap if dimensions were selected after measurements.
- Fixed an issue on combo chart where users were unable to set a limit on the x axis.
- Fixed an issue where the scatter chart did not re-plot points after a dimension is removed.
- Fixed an issue on combo chart where binning did not change for the smaller value when setting a date filter.
- Fixed an issue where the Export Dashboard filter was not working.
- Fixed mapd-connector to address poor query performance on large array columns.
- Fixed an issue where the horizontal axis lock did not hold when switching from line to histogram chart.
- Fixed an issue where turning off binning for large data sets could cause the browser to hang.
- Fixed an issue to combo charts where they were unable to render the range chart after placing a restrictive dimension filter.
- Fixed an issue where turning off binning on geo table could cause Immerse to stop.
- Improved performance of zoom/pan on line charts.
- Fixed an issue where the incorrect key symbol was displayed in the color palette after editing the line style.
- Fixed an infinite error loop when switching from choropleth to table chart.
- Fixed auto bin highlighting.
- Now supports mixed content: http web server, https backend.
- Fixed some combo chart interface inconsistencies.
4.0.2 - Released July 10, 2018
Fixed Issues
The following issues are fixed in version 4.0.2.
Migration Fixes
- Fixed transaction within transaction exception when upgrading to MapD version 4.0 or later.
Rendering Fixes
- Properly handle dictionary encoded strings inside a
CASE statement when used as input to a Vega transformation.
MapD Immerse Fixes
- Fixed latitude bounds sanitization on Mapbox chart render/zoom.
Other Fixes
- Improved the stability of
LAST_SAMPLE on dictionary encoded string columns
- Fixed incorrect result for certain queries on dictionary encoded strings in a distributed cluster.
- Fixed an issue where
GROUP BY on a Boolean column caused a system failure.
- Properly handle projecting TINYINT columns in a distributed cluster.
4.0.1 - Released July 6, 2018
Fixed Issues
The following issues are fixed in version 4.0.1.
Migration Fixes
- Sqlite3 Error: database is no longer locked after migration.
- Fixed a permission migration issue when the owner of the database is not a superuser.
- Fixed an issue that caused a system failure after copying geo data from csv in distributed cluster.
- Fixed an issue regarding migration of non-superuser dashboards from pre-4.0.
Rendering Fixes
- Fixed an issue where
aggxform is unable to access the alias map when no results are returned.
- Fixed
Invalid dimensions for texture array exception when rendering a geo pointmap in a distributed environment.
- Fixed an issue with aggregating and compositing a geospatial point render.
Other Fixes
- Fixed an issue that caused a segfault in
UPDATE, DELETE, DROP, and CREATE stress test.
- Fixed an issue that caused a segfault if no rows are passed to
load_table.
- Fixed an issue with
COPY FROM with ARRAY.
- Fixed an issue where network geo import from SSL-requiring locations failed on Ubuntu/Docker.
REGEXP now falls back to CPU when required rather than report errors.- Added
DATE, TIME, TIMESTAMP support for pymapd and all Arrow consumers.
- Volta performance has been improved.
- Fixed an issue that caused a system failure with
LAST_SAMPLE for certain high cardinality group bys.
- Fixed a
CHECK fail in reduceSingleRow() when using LAST_SAMPLE().
- Fixed inconsistency while building role map.
- Fixed an issue granting CREATE dashboard via role.
2.0.1.1 - Released December 20, 2016
MapD Core
Fixed
- Issue related to comparisons with
DATE ENCODING FIXED columns
- Added option to disable query watchdog via the command line option
--enable-watchdog=false
2.0.1 - Released December 16, 2016
MapD Core
Fixed
- Issue when calling
MIN/MAX on a TEXT ENCODING DICT column
- Performance regression with a high cardinality
GROUP BY
MapD Immerse
Fixed
- Issue with pointmap related to handling of out-of-bounds latitude/longitude values
Version 2.0
| Note |
Please note this version introduces a filesystem-level change to the on-disk
data. After the automated migration to this version has occurred, your data
directory will no longer be compatible with previous versions. Any risk is low,
but please confirm prior to starting a new version of MapD that your backups
are current and available. |
| Note |
This release breaks API compatibility with the previous JDBC driver. You
must use the new JDBC driver included in this release with any MapD Core 2.0
instances. |
| Note |
Version 2 of the MapD visualization web client, Immerse, now is available at
the root of the host, e.g. yourserver/. Version 1 of Immerse is still
available at yourserver/v1/. Links to saved version 1 dashboards will
resolve to the correct address. Version 1 is deprecated, but will continue to
be included in the MapD install, with sufficient notice to be given before it
is removed. Henceforth, updates to Immerse will be noted in these release
notes. |
2.0.0 - Released December 13, 2016
MapD Core
| Note |
Please note this version introduces a filesystem-level change to the on-disk
data. After the automated migration to this version has occurred, your data
directory will no longer be compatible with previous versions. Any risk is low,
but please confirm prior to starting a new version of MapD that your backups
are current and available. |
| Note |
This release breaks API compatibility with the previous JDBC driver. You
must use the new JDBC driver included in this release with any MapD Core 2.0
instances. |
New
- Queries with multiple
GROUP BY columns perform significantly better than before, particularly for queries which generate a high number of groups
- Projection queries without a limit are now allowed most of the time, depending on filter selectivity
- Multi-column
GROUP BY now uses less memory
COPY TO now accepts any query allowed elsewhere in the system- More
IN / NOT IN subqueries are supported and have better performance
ATAN function support- Up to 30% faster StreamInsert and
COPY FROM import performance
- Support for polygon hit testing (checking whether a backend-rendered pixel has an underlying polygon)
- In addition to standard CSS-string color representations, colors can now be represented in a packed 32-bit integer format
- SQL watchdog now enabled by default, to catch queries which would consume excessive resources
- Glob support for
COPY FROM statement, allowing multiple delimited files to be specified for import
- Newly available
EXPLAIN CALCITE statement show human-readable relational algebra
- Full schema now reported in MapDQL when using
\d option
- Improved import times for small files
- Smaller, 2MB JDBC driver now available
- SQLImporter default behavior changed to append, if appropriate table is already available. Truncate option is now required to be specified if you want to import into an empty table.
Fixed
- Issue with
ORDER BY non-COUNT aggregates for queries which generate many groups
- Data race condition with 3+ way
JOIN
- Issue with
ORDER BY negative floats
- Issue with
ORDER BY a column when a function of that column is projected
- Issue with
IN subqueries when inner query is a projection query
- Robustness issues with simple top count queries which generate many groups before the top operation
- Issue with
LIKE / REGEX on non-dictionary encoded strings
- Issue when
CASE expression is an argument to a COUNT aggregate expression
- Issue when
TRUNCATE on integers when second argument is negative
- Issue when using
SELECT * from a 3+ way JOIN query
- Fixing edge-case Rendering bugs when updating Vega-only without changing SQL query
- Render polygon stroking issue when two adjacent polygon edges overlap one another
- Cleanup long-lasting HTTP connections caused by misbehaving clients. Timeout duration is configurable.
- Issue in a scenario where a table had been named A then renamed to B, then dropped and recreated as A
- Greater precision is now maintained for Lat/lon on rendered maps
- JDBC connector mishandling of
AS in SQL statements
- Issue with importing
DATE or TIMESTAMP as a negative UNIX epoch time representation
- Issue with
COPY TO for TIME columns
- Issue with Linux kernel memory fragmentation
- Issue with JMeter support in the JDBC driver
MapD Immerse
| Note |
Version 2 of the MapD visualization web client, Immerse, now is available at
the root of the host, e.g. yourserver/. Version 1 of Immerse is still
available at yourserver/v1/. Links to saved version 1 dashboards will
resolve to the correct address. Version 1 is deprecated, but will continue to
be included in the MapD install, with sufficient notice to be given before it
is removed. Henceforth, updates to Immerse will be noted in these release
notes. |
1.2.10 - Released November 3, 2016
MapD Core
New
- Now supporting
JOIN for three or more tables
- Faster loading of cold data from disk
- More detailed error messages for unsupported
JOIN queries
- Enhanced precision when rendering
double columns for X/Y
- New mapdql command
\memory_summary to show current memory usage
Fixed
- Issue with
SORT queries containing duplicate count all aggregates
- Incorrect results for
OUTER JOIN queries with a projection CASE involving NULLs
COUNT DISTINCT for 2 or more columns now properly rejected- Issue with instability when close to limit of physical host memory
- Inaccurate results for
SUM and AVERAGE for floating point on
GPU
- Conversion from string to numeric types on
INSERT statement
CAST from integer to float for literal constants- Issue with
bigint interpretation in JDBC
1.2.9 - Released October 17, 2016
MapD Core
New
- Scalar subqueries may now be run without enabling loop joins
- Allow fully qualified columns not specified in project portion of
query to be used in
ORDER BY
- Additional multi-column
GROUP BY queries now run on GPU
Fixed
- Issue with sub-queries having empty intermediate results
- Issue with
CASE statements without a specified ELSE branch
COUNT on non-dictionary encoded strings used in a GROUP BY- Issue with
MIN or MAX on a string in a GROUP BY query
- Reliably throw exception instead of returning empty results for
division by zero
- Now short-circuiting logical expressions
1.2.8 - Released October 3, 2016
MapD Core
New
- Text columns now default to dictionary encoding. If old unencoded
behavior required then
TEXT ENCODING NONE should be used in
create table statement. This does not affect existing tables,
but any new tables created are affected.
- Now able to color by boolean
Fixed
- Issue for some
CASE statements involving nullability
- Issue with sort on very high cardinality column
- Now throwing exception on overflow for arithmetic operations
- Allow hash joins rather than loop joins in queries with
ORDER BY
- Issue when trying to
GROUP BY array column
- Issue with
OR statements involving NULLs
- Issue in comparing decimal column with integer literal
- Issue for any string literal containing the term
all or other SQL
tokens
- Now throwing exception for tables with very high number of columns
1.2.7 - Released September 12, 2016
MapD Core
New
- Add support in JDBC driver for implicit type casting of expressions
to double/string, not requiring explicit CAST operator
1.2.6 - Released September 6, 2016
MapD Core
New
- Support for POSIX regular expressions, boolean match
- Performance improvement for some
GROUP BY ORDER BY queries
with a LIMIT
- Added NVARCHAR support to SQLImporter
- Added function distance_in_meters
- Now supporting sub-pixel morphological anti-aliasing, for better line
anti-aliasing
Fixed
- Problem when coloring by string with null value
- Failure to update pointmap color when range of the scale changes
- Parsing problem with SQL text containing “all” or “any”
1.2.5 - Released August 23, 2016
MapD Core
New
- Improvement in memory efficiency for
GROUP BY unnested string
arrays
- Added fragment size option to SQL Importer
- Optimization to leverage hardware-accelerated FP64 atomics on Pascal
architecture
- Improved stability and performance for high cardinality group by
queries
Fixed
- Issue with multi-key
GROUP BY on empty table
- Regression with coloring by string on backend rendered images
- Issue on certain hardware where backend rendered pointmap images draw
to a corner/side
1.2.4 - Released August 15, 2016
MapD Core
New
EXTRACT week supportTRUNCATE support for non-decimal numeric typesCAST from timestamp to date- Partial
INTERVAL support
- Performance improvement for
GROUP BY date
- Additional performance optimizations for subqueries
LOG10 support- Backend rendering now supports all quantitative scales in vega
specification, including pow, sqrt, and log
Fixed
- Fixed an issue with Postgres importer reporting boolean as bit
- Fixed occasional slowdown for render queries on servers with many
GPUs
- Fixed an issue affecting non-
GPOUP BY queries on an empty table
- Fixed an issue when selecting
MIN or MAX from empty table
- Fixed an issue for
IN subqueries when inner query result is above a
certain size
- Fixed an issue with performance for “top n” queries
1.2.3 - Released August 1, 2016
MapD Core
New
- Now allow using aliases in
FROM and WHERE clauses
Fixed
- Made loading from cold cache (disk) faster
- Fixed memory leaks around unsupported queries
- Fixed problem when recreating a previously dropped table
- Fixed problem when parsing CSVs with inconsistent number of columns
1.2.2 - Released July 25, 2016
MapD Core
New
- Added math functions
(
ACOS,ASIN,ATAN,ATAN2,COS,COT,SIN,TAN,ABS,CEIL,DEGREES,EXP,FLOOR,LN,LOG,MOD,PI,POWER,RADIANS,ROUND,SIGN)
- Improved performance for top k IN subqueries
- Added partial support for NOT IN subqueries
- Added automatic reprojection of lat/long to mercator for mapping
display
Fixed
- Fixed an issue for CAST from a literal decimal
- Fixed CAST of NULL to a numeric type
- Fixed unary minus operator for nullable inputs
1.2.1 - Released July 18, 2016
MapD Core
New
- Backend rendered images can now be colored along a spectrum between
two colors, based on an accumulated measure (e.g. accumulated red or
blue datapoints can result in purple)
- Added
DROP and ALTER table support for Apache Calcite
Fixed
- Added a more robust conversion of decimal literals to float,
retaining more precision
- Fixed an issue for
CASE expressions which return booleans
1.2.0 - Released July 11, 2016
MapD Core
New
- Changed SQL parser to Apache Calcite
- Subquery support
- Further join support (e.g. left outer join)
- Case insensitivity for column and table names
- New core execution engine, Relational Algebra Virtual Machine
(“RAVM”), gives more flexibility allowing execution of arbitrarily
complex queries
- Added additional formats for date import
- MapD Immerse v.2 technical preview
- Redesigned user interface allows more powerful chart creation and
intuitive data exploration
- To access the Immerse Technical Preview Dashboards page, go to
http://<server>:<port>/v2/
- Immerse v.2 technical preview is an unstable preview release. A
subset of major known bugs is here
Fixed
- Fixed a problem with count distinct and group by queries
- Fixed a problem with count on float
- Fixed a problem with projection queries in limited cases
- Fixed a problem where tables created via MapD web-based table
importer were not consistent with tables built via SQL CREATE
- Disallowed use of reserved SQL keywords as column names
Removed
- Loss of Group By ordinals (would restore pending Calcite support)
Dependencies
- Now requiring Java Runtime Environment (JRE) version 1.6 or higher
Version 1.1
1.1.9 - Released June 27, 2016
MapD Core
New
- Improved logging and system process management
- Deprecated
--disable-fork flag in mapd_server. Please remove
this flag from any config files.
- Removed
fork() from mapd_server. Automatic restart should now
be handled by an external process, such as systemd.
- Added graceful shutdown to
mapd_web_server so that systemd more accurately reports its status
- Modified
mapd_server service file so that systemd more
accurately reports its status
- Improved logging of various mapd_server operations
- Improved memory handling to better maximize GPU RAM usage
Fixed
- Fixed a bug that prevented queries from running which were joining an
empty table
- Fixed a subtle stroke/line visual defect when polygons are rendered
on the backend
1.1.8 — Released June 21, 2016
MapD Core
New
- Added
\copygeo command to support ingesting shapefiles
- Added backend API for rendering polygons
Fixed
- Improved performance of
CASE queries that don’t have an ELSE clause
- Fixed a crash that would occur when certain large output results were
generated
- Improved performance of queries, such as
SELECT * FROM table_name LIMIT 5
- Fixed a bug that would sometimes omit results from queries with
AVG where NULLs were present
1.1.7 — Released June 13, 2016
MapD Core
Fixed
- Fixed bug where certain long-running queries would needlessly block
others
- Immerse: fixed a problem where embedding apostrophes or % in filters
or custom filters could cause errors
- Immerse: added MapDCon example for Node.js
1.1.6 — Released May 31, 2016
MapD Core
New
- Added Apache Sqoop support to the MapD JDBC driver. Please contact us
at
support@mapd.com to obtain the JDBC driver.
- Improved performance when grouping on
date_trunc with additional
columns
Fixed
- Fixed a bug that would appear when calculated fields tried to divide
by zero
- Fixed bug with CASE expressions
- Fixed bug where COPY statement blocks execution of other queries
1.1.5 — Released May 23, 2016
MapD Core
New
- Improved error logging to reveal the root kernel launch error for
group by queries
- Added a new API endpoint
sql_validate to the API
Fixed
- Fixed a bug that calculated incorrect results on
COUNT(CASE....) style conditional counting queries
- Fixed a memory usage and performance bug which was causing some
render API calls to timeout
1.1.4 — Released May 16, 2016
MapD Core
New
- Improved memory fragmentation handling by adding support for huge
pages.
- Improved performance when joining large tables to small tables.
- Improved join on dictionary strings performance.
Fixed
- Fixed out-of-bound access in VRAM when out-of-slot exception raised
- Fixed an issue with queries returning empty result sets
- More conservative tuple threshold for compaction, fixing count
overflow on large tables
- Reduced memory fragmentation for long-running servers
1.1.3 — Released May 9, 2016
MapD Core
New
- Added a new chart type: Number Chart. The Number Chart shows a
single value, making it simpler to point out important averages,
totals, etc.
- Added a
--quiet flag to mapdql to supress it’s informational
messages from appearing in STDOUT
- Added frontend-rendered choropleth overlays to Point Map charts
- Added a watchdog capability to catch SQL queries that are poorly
formulated
- Improved the Database Engine log messages to improve readability, and
consistency
- Improved the
render() API to work with more column types. You can
now color output by values taken from your boolean and decimal
columns
Fixed
- Fixed a bug that caused Bar Charts to jump around when users
clicked on certain rows in long multi-page chart instances
- Fixed a bug where the CSV import logic prevented some quoted empty
strings from being handled properly
- Fixed a bug where the CSV import logic rejected rows with empty
strings in the last position
- Fixed a bug where the import logic wouldn’t properly handle string
arrays with embedded
NULL elements
- Fixed a bug where the SQL
AVG() function would introduce rounding
errors under some circumstances
- Fixed a bug where SQL statements with
JOIN and HAVING clauses
wouldn’t execute
This sitemap link is for the benefit of the search crawler.
