[KAFKA-13511] Add support for different unix precisions in TimestampConverter SMT

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.2.0
• Component/s: connect
• Labels: connect-transformation needs-kip
• Assignee: Julien Chanaud
• Reporter: Julien Chanaud
• Created: 07/Dec/21 14:08
• Updated: 22/Feb/22 16:17
• Resolved: 22/Feb/22 16:17

Description

Currently, the SMT TimestampConverter can convert Timestamp from either source String, Long or Date into target String, Long or Date.

The problem is that Long source or target is required to be epoch in milliseconds.

In many cases, epoch is represented with different precisions. This leads to several Jira tickets :

• KAFKA-12364
• KAFKA-10561

I propose to add a new config to TimestampConverter called "epoch.precision" which defaults to "millis" so as to not impact existing code, and allows for more precisions : seconds, millis, micros.

"transforms": "TimestampConverter",
"transforms.TimestampConverter.type": "org.apache.kafka.connect.transforms.TimestampConverter$Value",
"transforms.TimestampConverter.field": "event_date",
"transforms.TimestampConverter.epoch.precision": "micros",
"transforms.TimestampConverter.target.type": "Timestamp"

Exactly like "format" field which is used as input when the source in String and output when the target.type is string, this new field would be used as input when the field is Long, and as output when the target.type is "unix"

Issue Links

• links to: GitHub Pull Request #11575
• links to: KIP-808: Add support for unix epoch precision in TimestampConverter SMT