> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/devops/pro-code/custom-cdc-managers.md).

# Custom CDC Managers

Custom CDC managers can be created and added to track changes in different systems, if needed.

All CDC managers extend the abstract CDCManager class or one of its subclasses.

```java
public class MyCDCManager extends CDCManager{

  /** 
   * Constructor with provided "alias", as well as its configurations.
   * Note: CDCManagers are not necessarily managed by EventRunners,
   * which is why they don't have access to them.
   */
  public MyCDCManager(String name, Map<String, String> config) {
    super(name, config);
  }
  
  /** 
   * Function called at the beginning of CDC loop, typically used for
   * establishing connection and applying offet alignment.
   */
  @Override
  public void start() throws HotException {
  }
   
  /** 
   * Function called on each loop iteration, for receiving the next
   * record. If no new records are received, the loop sleeps for poll
   * period.
   */
  @Override
  public CDCRecord tryNext() throws HotException {
  }
   
  /** 
   * Function called at the end for closing CDC loop.
   */
  @Override
  public void close() throws IOException {
  }

}
```

{% hint style="info" %}
Base CDCManager class handles additional functionalities, such as polling for records, handling errors and retries.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rierino.com/devops/pro-code/custom-cdc-managers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.