apache/seatunnel

[Feature][Zeta] Support debug mode for zeta

Open

#9,764 opened on Aug 25, 2025

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Java (1,432 forks)batch import
Zetafeaturehelp wanted

Repository metrics

Stars
 (6,897 stars)
PR merge metrics
 (Avg merge 13d 21h) (143 merged PRs in 30d)

Description

Search before asking

  • I had searched in the feature and found no similar feature requirement.

Description

Implementing debug mode in zeta without writing data to the target database. Allows users to:

  1. Print the table structure and data output by the source;
  2. Print the table structure and data output by the transform;
  3. Print a preview of the create table sql created by the sink (https://github.com/apache/seatunnel/blob/dev/seatunnel-api/src/main/java/org/apache/seatunnel/api/table/catalog/Catalog.java#L325)
  4. Can specify the number of data entries to read (the default is 10).

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Research direction
Understand the SeaTunnel source code architecture, especially the Zeta module. Identify how data flows from source to transform to sink. Implement a debug mode that intercepts data before writing to target. Use Catalog.java to preview create table SQL. Add a configuration parameter to limit the number of data entries read.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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
GitJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70