[
https://issues.apache.org/jira/browse/SPARK-34427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284348#comment-17284348
]
L. C. Hsieh commented on SPARK-34427:
-------------------------------------
If I don't miss anything, SPARK-10816 has no active progress in more than two
years. I don't know about your intention here, but I don't really see that it
was actively pushed during such long time. Seems to me the effort was abandoned
there and it looks totally okay to me that others can work on it, isn't?
About assigning JIRA issue, I'm not sure if you really do not know but
basically I remember the committers can assign JIRA issues to themselves if
they are working on it. We don't assign the JIRA issues created by contributors
to ourselves, because it is really unfair. For JIRA issues created for our
ongoing work, this is like a convention by other committers too. It is for not
step on others toes.
If you are really against it in general, maybe you can raise a discussion to
formally disallow it in Spark community. I'm happy to follow it if we finally
have a consensus about it. Thanks.
> Session window support in SS
> ----------------------------
>
> Key: SPARK-34427
> URL: https://issues.apache.org/jira/browse/SPARK-34427
> Project: Spark
> Issue Type: New Feature
> Components: Structured Streaming
> Affects Versions: 3.2.0
> Reporter: L. C. Hsieh
> Priority: Major
>
> Currently structured streaming supports two kinds of windows: tumbling window
> and sliding window. Another useful window function is session window. Which
> is not supported by SS. We have user requirement to use session window. We'd
> like to have this support in the upstream.
> About session window, there is some info:
> https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/windows.html#session-windows.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
