Pulsar EventTime: Transitioning from UTC Epochs to Timezone-Aware Timestamps
0 reputation · 05 Feb 2025, 16:53 UTC
Message Timestamping and Regional Offsets
Apache Pulsar (version 2.11.x) utilizes a UTC epoch millisecond value for eventTime. While this ensures a consistent global timeline, it places the burden of regional time zone conversion and date interpretation entirely on the producer and consumer applications.
Consistency Constraints
Currently, brokers do not interpret or store timezone metadata. To convey regional offsets, developers often implement custom message properties (e.g., eventTimeZone). However, because the broker ignores these properties for internal logic, there is no native mechanism to ensure consistency across diverse consumer implementations or to perform broker-side windowing based on local time.
This creates a gap in stream processing pipelines where event-time windowing must align with specific regional calendars rather than a strict UTC timeline.
- Is there a documented path toward a native timezone-aware timestamp type in the Pulsar API?
- What is the recommended approach for maintaining regional date integrity without relying on non-standardized custom properties?
