Skip to main content

DCH 2.4

· 5 min read

What's New​

Version 2.4 introduces several key features and changes to improve stability, logging, and UI while preparing for future advancements.

Memory 4 Your AI (M4AI)​

Memory 4 Your AI is an innovative platform that leverages DCH to enhance pre-trained Large Language Models (LLMs) with graph-based contextual knowledge. It facilitates the development and management of specialized engineering agents, designed to provide domain-specific insights and automate complex, industry-focused tasks. This low-code tool enables the creation of virtual AI assistants with a deep understanding of context, terminology, and workflows, tailored to solve domain-specific challenges.

Version 2.4 also introduces a new UI (GBS Beta) which is set to replace Explorer and GBS UI in the future. In addition to supporting all M4AI features, the new UI includes a Model section that showcases target entities, relationships, and data sources offering a preview of the modern design and user experience DCH envisions for the future.

Changes to the nodeId Property Format​

The nodeId property, used in related APIs and the Explore application to reference graph objects, has undergone significant changes:

  • Previously, the nodeId was generated non-deterministically, meaning identical entities could receive different nodeId values after each re-import process.
  • In version 2.4, the nodeId generation now relies on the Business Key, ensuring consistent nodeId values for the same logical entity across re-imports. This change improves the reliability of graph operations and facilitates deep linking in client applications.
warning

After deploying version 2.4, all previously imported data must be reprocessed to reflect the new nodeId format. The updated format is not backward compatible with earlier versions. However, re-importing the source data is not required.

Centralized Logging​

A unified logging system has been introduced in this release, now utilized across all DCH services. Key improvements:

  • Previously, only GBS and EBS could leverage the internal log database, with limited access to GBS logs via a dedicated API.
  • Logging, traces, and metrics collection have been centralized with OpenSearch, replacing Jaeger and Prometheus. Relevant data is collected using OpenTelemetry.

For further information on using OpenSearch, refer to the updated documentation.

info

The previous log database remains intact and is not automatically deleted.

Workers API Update​

The Workers API has been upgraded to version 2 endpoints, with improvements to DAG logic. As a result, Load Plans must be regenerated to ensure proper functionality.

warning

If Load Plans are currently in use, their DAGs need to be regenerated following this update.

Enhanced List Operations for Property Value Conditions​

Graph Access Rules now support list operations in property value conditions. With the introduction of the all_in and any_in operators, managing list comparisons has become more efficient and straightforward. For detailed guidance, please refer to the latest documentation.

Removal of Hierarchical Relationship Support​

The ability to define relationships as hierarchical, previously used to represent hierarchical data structures in the graph, has been removed in this version. This feature was deemed unnecessary and offered no significant benefits.

Explorer Transitions to Maintenance Mode​

This release includes the first version of the new DCH UI, designed to replace both the Explorer application and the current GBS UI. As part of this transition:

  • Explorer and its backend have entered maintenance mode.
  • Only critical issues that prevent usage will be addressed in future updates.

Improvements​

  • [EBS] Update to .NET 9
  • [GBS] Update to .NET 9
  • [GBS] Process data in batches to improve performance and stability
  • [GBS] Simplify setup and maintenance of Keycloak realm
  • [GBS] Default properties are not displayed when creating a relationship
  • [GBS] Removed obsolete proc-ignored-properties configuration
  • [GBS] Improved error and info messages

Bug Fixes​

  • [GBS] Deleting multiple properties when creating a new entity leads to an error
  • [GBS] Empty source table leads to an error on import
  • [GBS] Editing a business key in business key builder is not possible
  • [GBS] De/selecting an entity multiple times multiplies properties in create entity from container form
  • [GBS] Wrong business key name is displayed when editing in business key builder

API Changes​

This release introduces several API changes to enhance usability and standardization.

Updates to GBS v2 Endpoints​

GBS v2 endpoints now return properly camel-cased JSON responses for improved consistency.

Removed Endpoints​

The following API endpoints have been removed in this release:

  • [EBS] GET /api/graph/query/views/{id}
  • [GBS] GET /api/workers/getWorkers
  • [GBS] POST /api/workers/addWorker
  • [GBS] POST /api/workers/editWorker
  • [GBS] DELETE /api/workers/deleteWorker
  • [GBS] POST /api/keycloak/client-scope
  • [GBS] GET /api/logs/getLogFilters
  • [GBS] POST /api/logs/getLogs
  • [GBS] POST /api/logs/getLogsSearch

Deprecations​

The following API endpoints have been deprecated:

  • [GBS] GET /api/workers/getWorker

Deployment Changes​

As part of this update, the following adjustments have been made to the deployment configuration.

Adapt Connection String and Neo4j Host in SysConfiguration​

  • {{ Release.Name }}-postgresql is now postgresql
  • {{ Release.Name }}-neo4j is now n4j

All services previously named {{ Release.Name }}-servicename have now been switched to servicename, except for neo4j. This exemption for neo4j is due to the standard pod environment variables podname_* interfering with the system environment variables neo4j_* when the pod name is neo4j.