DCH 2.6
What's New
Version 2.6 of the DCH stack includes the following new features and changes.
Exploration Session in GBS and Removal of Explorer
The new Exploration Session feature has been introduced in the GBS UI, providing a user-friendly and intuitive way to navigate graph data. Users can now:
- Select data using labels.
- Search for specific data points.
- Explore data dynamically by adding related nodes and resolving paths between nodes.
With the addition of this enhanced feature in GBS, the Explorer and its backend are now obsolete and have been removed from the stack.
Introducing Neo4j Enterprise Edition
Starting with this release, Data Context Hub integrates with Neo4j Enterprise Edition, leveraging its powerful graph database capabilities to enhance data management and insight.
Additionally, Single Sign-On (SSO) via Keycloak has been enabled. Roles in Keycloak are mapped to Neo4j built-in roles to streamline permissions management. See the official Neo4j documentation for more details.
| DCH role | Neo4j role | Privileges |
|---|---|---|
| dch-admin | admin | Full access |
| dch-modify | editor | Read and write access |
| dch-execute | reader | Read-only access |
Queue Jobs Overview
The Queue Jobs Overview feature has been successfully ported to the new GBS UI, featuring:
- Enhanced job tracking with detailed stage visualization
- Improved integration with the worker-based intake system
- Streamlined monitoring of system processes
Removal of Artifact Support
In previous versions, artifacts were used for attaching additional data, such as images, links, and other binary files, to graph nodes. This functionality has now been replaced by the stack's AI-based approach, which offers a superior alternative. As a result, artifact support has been removed in this release.
Changes to Default Properties
Previously, the following properties were automatically added to all Target Entities:
- Title
- Description
- Reference_Date
- [Entity_title]_ID
As "Title" and "Description" were primarily required by Explorer, they are no longer added automatically to new Target Entities. Other properties that are used internally have been renamed and are now hidden from users for clarity.
The "Title" and "Description" properties will remain unchanged in existing Target Entities and will not be removed during this update.
The following columns are changed in content databases:
| Old Name | New Name | Comment |
|---|---|---|
${targetEntity}_ID | dch__id | |
Reference_Date | dch__importedAt | |
xpl_isUpdated | dch__isUpdated | |
Reference_Date | dch__importedAt | |
${targetEntity}_REL_ID | dch__relId | _REL tables |
${targetEntity}_ID | RelationFromId | _REL tables |
The following properties are changed in the graph:
| Old Name | New Name | Comment |
|---|---|---|
xpl_businessKey | dch__businessKey | |
xpl_dateProcessed | dch__processedAt | |
dch__importedAt | new property |
Property names starting with dch__ prefix are reserved for internal use and are not allowed to be added to target entities.
After deploying version 2.6, all previously imported data must be cleaned from the graph and processed again to follow internal property renames. The updated format is not backward compatible with earlier versions. However, re-importing the source data is not required.
Simplified License Modules and Role Management
License modules and role management have been streamlined to reduce the complexity in both ordering and access management:
License Changes:
- Base functionality is now included in the core license
- Only add-on modules remain separate
- Data Pump-specific modules are deprecated (supported while Data Pumps exist)
New Role Structure: The complex module-based role system has been replaced with three simplified roles:
dch-admin: Complete system access with full administrative privilegesdch-modify: View, modify, and execute operations (excluding administrative functions)dch-execute: View and execute operations without modification capabilities
These roles are now also used for OpenSearch and supersede the previously used opensearch-admin and opensearch-discover
roles.
Module-based roles are automatically removed from Keycloak during the upgrade.
API Changes
This release introduces several API changes to enhance usability and standardization.
Deprecations
The following APIs have been deprecated:
| API | Endpoints | Comments |
|---|---|---|
| GBS | /api/targetEntities/* | /api/v2/target-entities/* should be used instead. |
| GBS | /api/relationship/* | /api/v2/relationships/* should be used instead |
| GBS | /api/datapump/* | /api/v2/data-sources/* should be used for readonly access. There is no replacement for management endpoints, migration to data provider worker is encouraged instead |
| GBS | /api/dataimporter/* | /api/v2/data-intake-jobs should be used to run import jobs |
| GBS | /api/graphprocessing/* | /api/v2/data-intake-jobs should be used to run graph processing jobs |
| GBS | /api/queuejob/* | /api/v2/queue-jobs/* should be used instead |
Deployment Changes
As part of this update, the following adjustments have been made to the deployment configuration.
Removal of Explorer
With the removal of Explorer and Explorer Backend, the respective configuration can be removed from values.yaml.