debezium/dbz

Remove the predicate object from transform payload if no predicate is present

Closed

#2,308 opened on Jul 28, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)HTML (6 forks)auto 404
component/debezium-platformcomponent/user-interface-backendgood first issuetype/bug

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (PR metrics pending)

Description

Bug report

What Debezium connector do you use and what version?

Debezium platform

What is the connector configuration?

<Your answer>

What behavior do you expect?

It should return predicate: {} or no predicate object at all in case of no predicates are specified.

What behavior do you see?

Currently, the transform API /transforms GET return the predicate object even in the case of no predicate defined

{"id":14,"name":"Debezium marker without pridicate","description":"Extract Debezium payload","type":"io.debezium.transforms.ExtractNewRecordState","schema":"string","vaults":[],"config":{"add.fields":"op","add.headers":"db,table"},"predicate":{"type":null,"config":null,"negate":false}}

Contributor guide

Research direction
Investigate how the transform API constructs its response and locate where the predicate object is always included. Modify it to omit the predicate or return an empty object when no predicate is configured. Review existing tests for the transform API and add or adjust tests to cover the case of no predicate.
Tech stack
rest api
Domain
api
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80