[
https://issues.apache.org/jira/browse/SPARK-34427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284368#comment-17284368
]
L. C. Hsieh commented on SPARK-34427:
-------------------------------------
Please check the JIRA history and I don't think this is unconventional to
assign JIRA issue when there are ongoing works internally without PRs
submitted. This works in many years in Spark community.
Again, conventionally I do see the committers assign JIRA issues to themselves
or other contributors because they are working on it (even PR is not submitted
yet), or they plan to do it. That is how the Spark community does in the past
and now. So again, if you are against the convention, please raise a discussion
to disallow it. Otherwise I don't know why these issues are special for you.
We all need to plan what we want to do in Spark community. Opening JIRA issue
early can help gather thoughts from others. If we don't assign it, we can
easily step on others toes. From your perspective, once a JIRA issue is created
and we cannot assign it, it is open for others to work on it. How does the plan
work? Then I think no one will be willing to create JIRA issue before really
submitting PR.
We are experimenting RocksDB work internally so we create SPARK-34198 and
assign it. I don't know why it means we occupy major effort in parallel and
block others? So we can only work on one JIRA issue at a time?
I think these issues are not active in past years. I don't know why when we
want to push it and work on it, now we are blocking others???
I'm not saying that we definitely want to push our implementation for
SPARK-10816 by abandoning other two efforts in the past. But before any
communication ahead, it sounds too harsh to me that after we put the feature on
our plan explicitly, then there comes the claim that we should leave the work,
otherwise we are blocking others.
> 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: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
