What’s New in Gluesync 2.1

Gluesync 2.1 introduces powerful new features that enhance how you manage and organize your data integration pipelines. The highlight of this release is the introduction of Groups and Chains in the Core Hub, providing more control and flexibility in managing your data entities.

Introducing Groups and Chains

Gluesync 2.1 brings two powerful features to the Core Hub: Groups and Chains. These features transform how you organize and manage your data entities, making complex data integration scenarios more manageable and intuitive.

Groups: Logical organization made simple

Groups in Gluesync Core Hub serve as a logical grouping mechanism for entities, designed to simplify configuration and settings management across multiple related entities. Every new entity is automatically assigned to the "default" group unless specified otherwise.

Key benefits of Groups include:

  • Simplified management: Group related entities together for better organization

  • Efficient configuration: Apply settings to multiple entities simultaneously

  • Visual identification: Assign colors to groups for quick visual reference in the UI

  • Flexible organization: No impact on execution order or data flow

Chains: Managing entity dependencies

Chains are a specialized type of grouping that defines a physical execution order for entities. They are particularly valuable when working with entities that have foreign key relationships, ensuring operations are performed in the correct sequence to maintain data integrity.

With Chains, you can:

  • Define explicit execution order for related entities

  • Ensure referential integrity during data synchronization

  • Manage complex data relationships with ease

  • Visualize and control the flow of data between dependent entities

Getting started

To learn more about how to use Groups and Chains in your Gluesync implementation, visit our detailed guide: Groups and Chains Documentation.

User defined functions (UDFs)

Gluesync 2.1 introduces User Defined Functions (UDFs), a powerful feature that allows you to write custom code scripts executed during the data replication process in the Core Hub. UDFs enable you to implement custom business logic and transformations on your data as it flows through the system.

Custom business logic on your data

With UDFs, you can hook into the three main events that occur during data replication:

  • Insert operations: Process new records as they are created

  • Update operations: Transform data when existing records are modified

  • Delete operations: Implement custom logic when records are removed

This event-based execution model gives you fine-grained control over how your data is processed before reaching its destination.

Multiple language support

Core Hub’s UDF feature supports writing custom scripts in multiple programming languages:

  • Java

  • Kotlin

  • JavaScript (available soon)

  • Python (available soon)

You can select the language that best fits your team’s expertise and specific requirements.

Powerful data transformation

UDFs provide complete access to data context, enabling:

  • Sophisticated transformations based on business rules

  • Data validation and enrichment

  • Conditional processing based on record content

  • Custom filtering of records

Getting started with UDFs

To learn more about implementing User Defined Functions in your Gluesync environment, visit our detailed documentation: User Defined Functions documentation.

Automatic target table creation

Gluesync 2.1 introduces automatic target table creation, simplifying the process of setting up your data integration pipelines. This feature ensures that target tables are created automatically when needed, reducing the manual setup required and streamlining your workflow.

This feature comes with support for all the compatible RDBMS agents, including Oracle, IBM i DB2, and Microsoft SQL Server just to name a few.

The target table creation process is based on the source table schema, including column names, data types, and constraints. This ensures that the target table is created with the same structure as the source table, making it easier to maintain data integrity and consistency.

Need to intervene and modify the proposed target table create statement? No problem. You can always modify the proposed target table create statement manually by editing the proposed statement via our new code editor.

Enhanced TRUNCATE functionality

Gluesync 2.1 introduces enhanced TRUNCATE functionality that provides greater control over data management operations, particularly during snapshot processes and data synchronization workflows.

TRUNCATE before snapshot

When performing snapshot operations in INSERT mode, Gluesync 2.1 now supports automatic TRUNCATE operations before the snapshot for supported databases. This functionality ensures that target tables are cleared before the snapshot data is inserted, providing a clean slate for your data synchronization process.

Key benefits include:

  • Clean data state: Ensures target tables start fresh before snapshot insertion

  • Data consistency: Eliminates potential conflicts from existing data

  • Automated workflow: Reduces manual intervention in snapshot processes

  • Database compatibility: Works with all supported database systems

TRUNCATE command forwarding

Gluesync 2.1 also introduces TRUNCATE command forwarding capability, allowing TRUNCATE operations executed on supported source databases to be automatically forwarded to supported target databases. This feature maintains data consistency across your entire data ecosystem.

This functionality provides:

  • Real-time synchronization: TRUNCATE operations are immediately reflected across targets

  • Consistent data state: Ensures all connected databases maintain the same data structure

  • Automated propagation: No manual intervention required for TRUNCATE operations

  • Cross-platform support: Works across different database platforms and versions

Supported databases

The enhanced TRUNCATE functionality is available for all compatible RDBMS (source) agents supported by Gluesync:

  • Oracle (Xstream only)

  • IBM i DB2

  • PostgreSQL

  • YugabyteDB

  • Informix

Allowed Operations: Granular Control Over Data Synchronization

Gluesync 2.1 introduces a powerful new feature called Allowed Operations, which replaces and significantly enhances the previous "Skip Deletions" functionality. This feature provides fine-grained control over which database operations are synchronized between your source and target systems.

Key Enhancements Over Skip Deletions

  • Operation-Level Control: Now you can control four distinct operations: INSERT, UPDATE, DELETE, and TRUNCATE

  • More Granular: Configure allowed operations on a per-entity basis

  • Default Allow: All operations are enabled by default for new entities

  • Real-Time Application: Changes to operation settings take effect immediately

Common Use Cases

  • Audit Trails: Disable DELETE and TRUNCATE operations to maintain complete history

  • Data Archiving: Allow only INSERT operations to accumulate historical data

  • Read-Only Replicas: Enable only SELECT and UPDATE operations

  • Migration Scenarios: Temporarily disable TRUNCATE operations during critical periods

Getting Started

To configure Allowed Operations for an entity:

  1. Navigate to the entity configuration in Core Hub

  2. Locate the "Allowed Operations" section

  3. Select which operations should be allowed

  4. Save your configuration

For more detailed information, see the Allowed Operations documentation.

What’s next

This is just the beginning of our 2.1 release. We’re continuously working on enhancing Gluesync with new features and improvements. Stay tuned for more updates in our upcoming releases!