davidzollo opened a new issue, #10536:
URL: https://github.com/apache/seatunnel/issues/10536

   Sub-issue of #10533
   
   ## Scope
   
   `MultiTableSink` is the central adapter that wraps multiple per-table 
`SeaTunnelSink` instances into one unified sink. It has 207 lines and zero 
method-level Javadoc.
   
   ## File
   
   
`seatunnel-api/src/main/java/org/apache/seatunnel/api/sink/multitablesink/MultiTableSink.java`
   
   ## Methods to document
   
   | Method | Line | What to explain |
   |--------|------|-----------------|
   | `MultiTableSink(MultiTableFactoryContext)` | 59 | How the `sinks` map is 
populated from factory context; role of `replicaNum` — each subtask creates 
`replicaNum` writers per table to fill write queues |
   | `createWriter(SinkWriter.Context)` | 71 | Index formula `index = 
subtaskIndex * replicaNum + i` that distributes writers across queues |
   | `restoreWriter(SinkWriter.Context, List<MultiTableState>)` | 90 | How 
checkpoint states are matched back to per-table writers using `SinkIdentifier` |
   | `createCommitter()` | 130 | Aggregates per-table `SinkCommitter` instances 
into one `MultiTableSinkCommitter` |
   | `createAggregatedCommitter()` | 152 | Aggregates per-table 
`SinkAggregatedCommitter` instances |
   | `getSinkTables()` | 168 | Fallback logic: tries `getWriteCatalogTable()` 
first, falls back to extracting `TablePath` from sink plugin name |
   | `getWriteCatalogTable()` | 195 | Always returns `Optional.empty()` in 
multi-table context because catalog is managed per sub-sink |
   | `supports()` | 200 | Delegates schema evolution support check to sub-sinks 
|
   
   ## How to contribute
   
   1. Fork the repo and create a branch
   2. Add Javadoc to the methods above
   3. Run `./mvnw spotless:apply` and `./mvnw -q -DskipTests verify`
   4. Open a PR with title: `[Docs][Core] Add Javadoc to MultiTableSink`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to