[ 
https://issues.apache.org/jira/browse/KAFKA-18950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123396#comment-18123396
 ] 

Arti Kumari commented on KAFKA-18950:
-------------------------------------

Hi Sanghyeok,

Apologies, I could not close on it. Please take this further. I will pick
something else whenever i will have bandwidth.

Cheers,
Arti




-- 

Arti Kumari

Senior Software Engineer

<https://confluent.io>

Follow us: [image: RSS]
<https://www.confluent.io/blog/?utm_source=footer&utm_medium=email&utm_campaign=ch.email-signature_type.community_content.blog>[image:
LinkedIn] 
<https://www.linkedin.com/company/confluent/posts/?feedView=all>[image:
YouTube] <https://www.youtube.com/@Confluent>[image: Confluent Slack
Community]
<https://confluentcommunity.slack.com/join/shared_invite/zt-3az13rpkx-CMUmebJjiFwCn65VOaSEPA#/shared-invite/email>

<https://confluent.io/data-monster>


> Allow to "shift" window-start anchor for Tumbling/Hopping windows
> -----------------------------------------------------------------
>
>                 Key: KAFKA-18950
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18950
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Matthias J. Sax
>            Assignee: Arti Kumari
>            Priority: Major
>              Labels: needs-kip
>
> Tumbling/Hopping windows are well defined window boundaries by alining the 
> window start time to the UNIX epoch, ie, the very first window always start 
> at ts=0.
> It could be a useful addition, to allow users to control the start-time 
> "anchor" though, by adding an additional, optional "shift" parameter. This 
> would for example allow users, to start a "daily window" at noon, instead of 
> midnight.
> As long as we don't have "timezone" support, such a shift parameter should be 
> a workaround for daily windows which are currently anchored in UTC timezone...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to