tet123/documentation/modules/ROOT/pages/transformations/timezone-converter.adoc

211 lines
8.9 KiB
Plaintext
Raw Normal View History

:page-aliases: configuration/timezone-converter.adoc
[id="timezone-converter"]
= Timezone Converter
:toc:
:toc-placement: macro
:linkattrs:
:icons: font
:source-highlighter: highlight.js
toc::[]
[[timezone-converter-introduction]]
2023-09-05 14:11:11 +02:00
When {prodname} emits event records, the timezone values for timestamp fields in the record can vary depending on the type and configuration of the data source.
To maintain data consistency and precision within data processing pipelines and applications, you can use the `Timezone Converter` SMT to ensure that event records use a consistent timezone to represent timestamp data.
2023-09-05 14:11:11 +02:00
The SMT converts the value of the specified field to the target timezone by using the `converted.timezone` configuration option.
You can specify the target timezone as a geographic timezone, for example, `America/New_York`, or as a UTC offset, such as `+02:00`.
It is assumed that the fields of the record are in UTC.
2023-11-08 13:26:31 +01:00
Along with the specified timezone, the SMT also provides configuration options to include or exclude specific fields from timezone conversion using the `include.list` and `exclude.list` configuration options.
The SMT supports all Debezium and Kafka Connect temporal and non-temporal types.
[NOTE]
====
To comply with daylight savings time, you must specify a geographic timezone in the `converted.timezone` configuration option.
If you specify a UTC offset, the transform applies a fixed offset from UTC that isn't accurate for regions that observe daylight savings time.
Providing a fixed UTC offset is useful when converting timestamp fields to a specific timezone that does not observe daylight saving time.
====
[NOTE]
====
2023-11-08 13:26:31 +01:00
The `include.list` and `exclude.list` configuration options are mutually exclusive. You must specify only one of the options.
====
[[timezone-converter-usage]]
[[basic-example-timezone-converter]]
== Example: Basic configuration
Configure the `TimezoneConverter` SMT in the Kafka Connect configuration for a connector to convert the time-based fields in an event record to a target timezone.
For example, to convert all timestamp fields in an event record from UTC to the `Pacific/Easter` timezone, add the following lines to your connector configuration:
[source]
----
transforms=convertTimezone
transforms.convertTimezone.type=io.debezium.transforms.TimezoneConverter
transforms.convertTimezone.converted.timezone=Pacific/Easter
----
=== Effect of applying the `TimezoneConverter` SMT
The following examples show the timestamp fields in an event record before and after applying the `TimezoneConverter` transformation.
.Event record value before processing by the `TimezoneConverter` transformation
====
The value of the `created_at` field shows the UTC time.
[source, json]
----
{
"before": null,
"after": {
"id": 1,
"first_name": "Anne",
"last_name": "Kretchmar",
"email": "annek@noanswer.org",
"created_at": "2011-01-11T16:40:30.123456789+00:00"
},
"source": {
"version": "2.4.0.Aplha2",
"connector": "postgresql",
"name": "PostgreSQL_server",
"ts_ms": 1559033904863,
"snapshot": true,
"db": "postgres",
"sequence": "[\"24023119\",\"24023128\"]",
"schema": "public",
"table": "customers",
"txId": 555,
"lsn": 24023128,
"xmin": null
},
"op": "c",
"ts_ms": 1559033904863
}
----
====
.Event record value after processing by the `TimezoneConverter` transformation
====
The SMT converts the original UTC value of the `created_at` field to the time in the target `Pacific/Easter` timezone that is specified in the xref:basic-example-timezone-converter[Basic configuration] example.
The SMT also adds an `event_timestamp` field.
[source, json]
----
{
"before": null,
"after": {
"id": 1,
"first_name": "Anne",
"last_name": "Kretchmar",
"email": "annek@noanswer.org",
"created_at": "2011-01-11T11:40:30.123456789-05:00"
},
"source": {
"version": "2.4.0.Aplha2",
"connector": "postgresql",
"name": "PostgreSQL_server",
"ts_ms": 1559033904863,
"snapshot": true,
"db": "postgres",
"sequence": "[\"24023119\",\"24023128\"]",
"schema": "public",
"table": "customers",
"txId": 555,
"lsn": 24023128,
"xmin": null,
"id": 100
},
"op": "c",
"ts_ms": 1559033904863,
"event_timestamp": 1626102708861
}
----
====
[[advanced-example-timezone-converter]]
== Example: Advanced configuration
2023-09-05 14:11:11 +02:00
Instead of converting all timestamp fields in an event record, you can configure the SMT to convert specific fields only.
2023-11-08 13:26:31 +01:00
The following example shows how you might use the `include.list` option in the SMT configuration to convert only the `created_at`, and `updated_at` timestamp fields in an event record.
The following configuration uses a fixed offset, rather than a geographic timezone designator, to convert the time from UTC to `+05:30`.
[source]
----
transforms=convertTimezone
transforms.convertTimezone.type=io.debezium.transforms.TimezoneConverter
transforms.convertTimezone.converted.timezone=+05:30
2023-11-08 13:26:31 +01:00
transforms.convertTimezone.include.list=source:customers:created_at,customers:updated_at
----
In some cases, you might want to exclude specific timestamp fields from timezone conversion.
2023-11-08 13:26:31 +01:00
For example, to exclude the `updated_at` timestamp field in an event record from timezone conversion, use the `exclude.list` configuration option as in the following example:
[source]
----
transforms=convertTimezone
transforms.convertTimezone.type=io.debezium.transforms.TimezoneConverter
transforms.convertTimezone.converted.timezone=+05:30
2023-11-08 13:26:31 +01:00
transforms.convertTimezone.exclude.list=source:customers:updated_at
----
[[timezone-converter-configuration-options]]
== Configuration options
The following table lists the configuration options for the `TimezoneConverter` SMT.
.TimezoneConverter SMT configuration options
[cols="14%a,40%a,10%a,10%a"]
|===
|Property
|Description
|Type
|Importance
|[[timezone-converter-converted-timezone]]<<timezone-converter-converted-timezone, `converted.timezone`>>
|A string that specifies the target timezone to which the timestamp fields should be converted.
The target timezone can be specified as a geographic timezone, such as, `America/New_York`, or as a UTC offset, for example, `+02:00`.
|string
|high
2023-11-08 13:26:31 +01:00
|[[timezone-converter-include-list]]<<timezone-converter-include-list, `include.list`>>
|A comma-separated list of rules that specify the fields that the SMT includes for timezone conversion.
Specify rules by using one of the following formats:
`source:<tablename>` :: Matches {prodname} change events with source information blocks that have the specified table name.
The SMT converts all time-based fields in the matched table.
`source:<tablename>:<fieldname>` :: Matches {prodname} change events with source information blocks that have the specified table name.
The SMT converts only fields in the specified table that have the specified field name.
`topic:<topicname>` :: Matches events from the specified topic name, converting all time-based fields in the event record.
`topic:<topicname>:<fieldname>` :: Matches events from the specified topic name, and converts values for the specified fields only.
`<matchname>:<fieldname>` :: Applies a heuristic matching algorithm to match against the table name of the source information block, if present; otherwise, matches against the topic name.
The SMT converts values for the specified field name only.
|list
|medium
2023-11-08 13:26:31 +01:00
|[[timezone-converter-exclude-list]]<<timezone-converter-exclude-list, `exclude.list`>>
|A comma-separated list of rules that specify the fields to exclude from timezone conversion.
Specify rules by using one of the following formats:
`source:<tablename>` :: Matches {prodname} change events with source information blocks that have the specified table name.
The SMT excludes all time-based fields in the matched table from conversion.
`source:<tablename>:<fieldname>` :: Matches {prodname} change events with source information blocks that have the specified table name.
The SMT excludes from conversion fields in the specified table that match the specified field name.
`topic:<topicname>` :: Matches events from the specified topic name, and excludes from conversion all time-based fields in the topic.
`topic:<topicname>:<fieldname>` :: Matches events from the specified topic name, and excludes from conversion any fields in the topic that have the specified name.
`<matchname>:<fieldname>` :: Applies a heuristic matching algorithm to match against the table name of the source information block, if present; otherwise, matches against the topic name.
The SMT excludes from conversion only fields that have the specified name.
|list
|medium
|===