anchor.diff:  [[reading-the-commitlog]]
   === Reading the Commit Log
   
  -The Cassandra connector will typically spend the vast majority of its time reading local commit logs on the Cassandra node.
  +The Cassandra connector will typically spend the vast majority of its time reading local commit logs on the Cassandra node. In Cassandra 4.0 on every segment fsync, an index file will be updated to reflect latest offset. This eliminates the processing delay in the CDC feature in Cassandra 3.X. and can be enabled in Cassandra 4 Debezium connector by setting the configuration: `commit.log.real.time.processing.enabled` to `true`. The frequency at which index file is polled is determined by `commit.log.marked.complete.poll.interval.ms`.
  +
   
   Commit logs' binary data are deserialized with Cassandra's CommitLogReader and CommitLogReadHandler. Each deserialized object is called a `mutation` in Cassandra. A `mutation` contains one or more change events.
   
  
positive.code: |
  |The SSL config file path required for storage node. An example of config file can be found at the bottom of the page.
  
  |[[cassandra-property-commit-log-relocation-dir]]<<cassandra-property-commit-log-relocation-dir, `commit.log.relocation.dir`>>
  |
  |The local directory where commit logs get relocated to from cdc_raw dir once processed.
  
negative.code: * Due to the nature of CQL, _insert_ DMLs can result in a row insertion or update; _update_ DMLs can result in a row insertion, update, or deletion; _delete_ DMLs can result in a row update or deletion. Since queries are not recorded in commit logs, CDC event type is classified based on the effect on the row in a relational database sense.
  
  **TODO**: is there a way to determine event type which corresponds to the actual Cassandra DML statement? and if so, is that preferred over the semantic of these events?
  
  [[managing-commitlog-lifecycle]]
  === Managing Commit Log Lifecycle
  