Page History

...

• Export data into some warehouse, full-text search system, or distributed log system.
• Online statistics and analytics
• Wait and respond to some specific events or data changes.

...

• CDC application works as a separate process.
• CDC relies on the existing Ignite mechanism - WAL.
• IEP Scope - deliver local data change events to a local consumer.
• CDC keeps consumer offset in a special file.
  WAL process will start from this offset on restart.
• To prevent interference between the WAL archive process and CDC Ignite will create a hard link to the newly created segment in a special folder.
  After success processing, CDC will delete this link.
  Note, data will be removed from the disk only after CDC and Ignite will remove the link to a segment from both corresponding folders.
• To manage minimal event gap new configuration timeout introduced - WalForceArchiveTimeout.
• Flag to distinguish DataEntry on primary and backup nodes introduced.
• All public APIs market with @IgniteExperimental to be able to improve it based on real-world usage feedback.
• CDC consumer will be notified about binary metadata changes (Phase 2).
• Configuration parameter "Maximum CDC folder size" will be implemented to prevent disk volume exceed.
• CDC folder resolved using the logic as Ignite node does.
• CDC application should be restarted by the OS mechanism in case of any error (destination unavailability, for example)

CDCConsumer public API interface:

...