This section introduces the set of fundamental concepts and terminology used by e6data. Understanding these will help to use e6data effectively.

General Concepts

This section describes the general concepts employed by e6data.

An e6data account represents a single entity for handling all your e6data workloads within the e6data platform which includes billing and support.

A workspace is an asset that contains the supporting infrastructure for e6data engines to run inside your cloud environment. You can choose to have multiple workspaces or just one: it depends on your needs.

Clusters contain the compute that e6data uses to process queries. e6data Clusters are created using Kubernetes. Cluters can be connected to notebooks, BI tools, dashboards, etc. so your teams can query the data they need.

Catalogs (Metastores)

Catalogs or Metastores contain metadata describing the data sources your teams want to query. e6data supports multiple metastores like AWS Glue & Apache Hive. Catalogs and clusters support many-to-many relationships. You can give one or more clusters access to single or multiple catalogs based on your organization's data access or governance rules.

The Query Editor is a native SQL console on which you run your SQL queries within the e6data platform.

The Query History section contains a log of all the queries run in the query editor.

Within our platform, the Access Control feature grants users the ability to invite others and assign designated roles, each equipped with the necessary permissions. Access Control functionality is integral to ensuring robust security across the system.

Connectors can be used to integrate e6data with your existing querying tools (JDBC, ODBC, etc.) A full list of available connectors and configuration guides can be found here.

Last updated