What characterizes manual watermarks?

What characterizes manual watermarks?

• A. The user handles saving, retrieving, and comparing the watermark
• B. They are always managed automatically
• C. They cannot be persisted
• D. They are deprecated

Answer: (A)

Watermarks mark how far you’ve processed data, acting as a progress indicator for incremental loads. When watermarks are manual, you’re in charge of their lifecycle: after processing a batch, you save the watermark; when you start or resume, you load it; and you compare it to the new data to determine what remains to be processed. This gives you full control over durability and resumption logic, letting you store the watermark in a database, a file, or another persistent store. Automatic watermarks would be managed by the framework, which isn’t the case here. Since you control persistence, the watermark can be persisted, and there’s no inherent deprecation implied.

Watermarks mark how far you’ve processed data, acting as a progress indicator for incremental loads. When watermarks are manual, you’re in charge of their lifecycle: after processing a batch, you save the watermark; when you start or resume, you load it; and you compare it to the new data to determine what remains to be processed. This gives you full control over durability and resumption logic, letting you store the watermark in a database, a file, or another persistent store. Automatic watermarks would be managed by the framework, which isn’t the case here. Since you control persistence, the watermark can be persisted, and there’s no inherent deprecation implied.