Versions and compatibility
Manual versions
| Release | Status | Manual | Maintenance |
|---|---|---|---|
| 9.1.2 | Current | DAM manual | Current baseline; corrections and verification tracking |
| 9.2 | Planned for November 2026 | Plan | Unavailable before release; not a delivered capability commitment |
Online manuals are not backfilled for releases before 9.1.2. Before each release, freeze the previous baseline in both languages, then update the stable DAM entry points. Frozen content receives critical corrections, security fixes, and link repairs rather than current-feature rewrites.
Release numbers identify the DAM product baseline. Maintain changes by module rather than duplicating all content when only some modules change. See 9.1.2 notes and 9.2 plan.
Release controls
- Preview the archive with
npm run docs:version:archive:check -- <current-release>, then create a non-overwriting snapshot withnpm run docs:version:archive -- <current-release>. - Mark the old release
archivedwith snapshot paths and promote the new one fromplannedtocurrentin the registry. - Track additions, changes, retirements, source adapters, parsers, and APIs by module. Recheck reused pages and links.
- Verify menus, permissions, writes, approvals, deployment, connectors, parsers, and responses; record actual verification dates.
- Validate current and archived pages, both languages, PDFs, links, version switching, and search before release.
Planned versions are not navigable in the selector. Open them only after content review, compatibility checks, and acceptance.
Backend storage, metadata harvesting, SQLink parsing, and gateway access are separate compatibility scopes.
Read the support matrix
Supported means capability is recorded in product materials, not that every edition, driver, charset, and topology is certified. Unlisted native support can be assessed through custom drivers or similar SQL dialects, with separate target testing. Unspecified versions remain unspecified.
Language support
| Language | DAM | SQLink | DIG | User manual |
|---|---|---|---|---|
| Simplified Chinese | Supported | Supported | Supported | Supported |
| English | Supported | Supported | Supported | Supported |
Platform databases
| Type | Database | Explicit version | Scope |
|---|---|---|---|
| Relational | MySQL | 8.0.35 | DAM platform persistence |
| Relational | PostgreSQL | 14.6 | DAM platform persistence |
| Relational | Oracle | 11g | DAM platform persistence |
| Relational | DM Database | 8 | DAM platform persistence |
| Graph | NebulaGraph | 3.8.0 | Lineage and SQLink |
Database and SQL script support
The following matrix is updated from the latest support list. Supported and Not supported are explicit source-list conclusions; a blank capability means the source does not state it and is not interpreted automatically.
For a source marked Not supported for metadata harvesting, use a custom data source (custom connector or driver) as an alternative. For a source marked Not supported for lineage parsing, use a parser for a similar database engine or SQL dialect. Validate each alternative against the target environment, release, and SQL features; this does not change the native support conclusion in the matrix.
| Database or SQL script | Metadata harvesting | Lineage parsing | Security Gateway | Notes |
|---|---|---|---|---|
| Cassandra | Not supported | Not supported | — | — |
| CBASE | Not supported | Not supported | — | — |
| ClickHouse | Supported | Supported | — | — |
| DM Database | Supported | Supported | — | Added in 9.1 |
| IBM DB2 | Supported | Supported | Supported | Security Gateway added in 9.1.2 |
| Elasticsearch | Supported | Not supported | — | — |
| FusionInsight | Supported | Supported | — | — |
| GaussDB | Supported | Supported | — | — |
| GBase | Supported | Supported | — | Enhanced in 9.1 |
| Greenplum | Supported | Supported | — | — |
| HashData | Not supported | Not supported | — | Try another engine |
| HBase | Supported | Supported | — | — |
| Hive | Supported | Supported | Supported | — |
| Hologres | Supported | Supported | — | — |
| Impala | Supported | Supported | — | — |
| MaxCompute | Supported | Supported | — | Enhanced in 9.1 |
| MongoDB | Supported | Not supported | — | — |
| MySQL | Supported | Supported | Supported | — |
| OceanBase-MySQL | Supported | Supported | — | — |
| OceanBase-Oracle | Supported | Supported | — | — |
| openGauss | Supported | Supported | — | — |
| Oracle | Supported | Supported | Supported | — |
| PolarDB-MySQL | Supported | Supported | — | — |
| PolarDB-Oracle | Supported | Supported | — | — |
| PostgreSQL | Supported | Supported | — | — |
| SAP HANA | Supported | Not supported | — | Try another engine |
| Spark | Not supported | Supported | — | — |
| SQL Server | Supported | Supported | — | — |
| StarRocks | Supported | Supported | — | Enhanced in 9.1 |
| Teradata | Supported | Supported | — | — |
| TiDB | Not supported | Not supported | — | Try another engine |
| Transwarp-Inceptor | Supported | Supported | — | — |
| Vertica | Supported | Supported | Supported | Security Gateway added in 9.1.2 |
| Databricks | Supported | Not supported | — | Added in 9.1.2; try another engine |
| Snowflake | Supported | Not supported | — | Added in 9.1.2; try another engine |
| Azure Synapse Analytics | Supported | Not supported | — | Added in 9.1.2; try another engine |
| Amazon Redshift | Supported | Not supported | — | Added in 9.1.2; try another engine |
| Google BigQuery | Supported | Not supported | — | Added in 9.1.2; try another engine |
Reporting tools
| Reporting tool | Explicit version | Metadata harvesting | Lineage parsing | Notes |
|---|---|---|---|---|
| YongHong BI | 10.2.0.2 | Supported | — | — |
| Cognos | — | Supported | — | — |
| Fine BI | 5.1 | Supported | Supported | — |
| Fine Report | 10.0 | Supported | Supported | — |
| SmartBI | — | Supported | Supported | Added in 9.1 |
| Davinci | — | Supported | — | — |
| Oracle Analytics Server | — | Supported | Supported | Enhanced in 9.1.2 with RPD report model support |
| Custom reports (DAM) | — | Supported | — | Bug fix in 9.1.2 |
| MS PowerBI | — | Supported | Supported | Added in 9.1.2 |
| Tableau | — | Supported | Supported | Added in 9.1.2 |
| Qlik Sense Enterprise | — | Supported | Supported | Added in 9.1.2 |
| Datablau custom reports | — | Supported | Supported | Added in 9.1.2; SQL parsing supported |
ETL and job tools
| Tool | Support status | Notes |
|---|---|---|
| SSIS (Microsoft SQL Server Integration Services) | Supported | — |
| DataStage (IBM) | Supported | — |
| PowerCenter (Informatica) | Supported | — |
| Kettle (Pentaho Data Integration) | Supported | — |
| DataX (Alibaba) | Supported | MaxCompute format added in 9.1 |
| Apache Sqoop | Supported | — |
| OpenLineage | Supported | Standalone enhancement in 9.1.2 |
| RestCloud ETL | Supported | — |
| Excel custom lineage | Supported | — |
| DBLink | Supported | — |
| SeaTunnel | Supported | Added in 9.1.2 |
| WhaleTunnel | Supported | Added in 9.1.2 |
| Fine DataLink | Supported | Added in 9.1.2 |
| Alteryx | Supported | Added in 9.1.2 |
Packages cover AWS Redshift, Azure Synapse, Databricks, FineDataLink, Google BigQuery, OpenLineage, SeaTunnel, and Snowflake. Verify package versions, formats, and parsing scope. The demo package is illustrative, not a supported product item.
Security Gateway and JDBC Driver
The Security Gateway is a dynamic-masking module with a compatibility scope separate from metadata harvesting and SQLink parsing. The latest support list explicitly marks IBM DB2, Hive, MySQL, Oracle, and Vertica as supported. Validate other databases against the target environment.
| Item | Confirmed information |
|---|---|
| Connection | Datablau JDBC Driver to Security Gateway |
| Driver class | com.datablau.jdbc.Driver |
| URL example | jdbc:datablau://[host]:[port] |
| Database types | IBM DB2, Hive, MySQL, Oracle, Vertica |
| Driver version | Unspecified |
| Authentication combinations | Validate the target database, driver package, and gateway settings |
Before onboarding
- Identify storage, harvesting, parsing, or gateway scope.
- Confirm account permissions for the target capability.
- Test the actual connector/driver, then a small harvest or parse. Validate custom drivers and dialects separately.
- Check charset, allowlists, SSL, timeout, and large-object handling.
- Record database version, driver checksum, results, and failure logs.
This reference does not replace deployment acceptance. Ask the product team to assess unlisted databases, versions, and tools; actual tests determine usable scope.