Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Section

Support Engineer Plugin - System & Usage Report

The 'System & Usage Report' now contains the customer`s meta data information which is needed in support cases and provides a higher level overview. Therefore all technical environment information can be reported. Only the administrator can view the system report as well as download the report files individually.

...

Section

Improved UI for Admin Variables

Datameer improved the UI for the Admin Variables.

Section

Configuring Network Proxy for S3 Native

S3 proxy settings now apply for S3 native connections.

...

Section

Google Cloud Connectivity

Google Cloud Data Proc as Execution Engine

Google Cloud DataProc v1.2 supports all Datameer jobs (e.g. workbooks, import, export, system jobs) to be executed within Google DataProc. All job results are stored in HDFS. With this feature you can run Datameer on their existing Google Cloud offering. This avoids maintaining a second storage account and transferring large datasets from Google into other cloud solutions (e.g. Microsoft Azure).

Google Cloud Storage Import & Export

Datameer now supports import and export from Google Cloud Storage.

Therefore we provide the plugin "plugin-gcs" which contains the connector to Datameer. With the Google Cloud Storage import connector you can ingest data from Google Cloud Storage and enable joining and aggregation or data moving. With the Google Cloud Storage export connector you can expose data from Datameer into Google Cloud Storage and continue on working of prepared, cleaned and aggregated data with other 3rd party systems.

Google Cloud Storage Private Folder

You can now build and set up Datameer with Google Cloud Storage as a Private Folder. Datameer's job results can be stored in a Google Cloud Storage Private Folder.

Performance Improvement

Section

Join Operation Computes Parallel Inputs

A join of two data links now computes inputs in parallel to prevent the creation of too many DAG(s) on the cluster, and the Map-Side join picks the smallest of the two inputs to cache in memory.

...