[ https://issues.apache.org/jira/browse/SPARK-34427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284362#comment-17284362 ]
Jungtaek Lim edited comment on SPARK-34427 at 2/14/21, 7:28 AM: ---------------------------------------------------------------- I'd say SPARK-10816 has no active progress so far because of lack of interest. Once you found the necessity then SPARK-10816 can be unblocked instead of spending another non-trivial time to reinvent the wheel, no? See SPARK-10816, there're SPIP docs, discussions, ideas around them, even perf tests on WIP PRs. These efforts were actually more than a month. What this issue provides? It's just a simple link Flink provides. No design doc, no implementation, no test. This JIRA issue basically does nothing yet. That said, it's far behind than the existing effort. You can't simply say existing PR is complicated than you have in mind unless you can prove it via similar sort of effort, SPIP doc with design doc. I pointed out JIRA issue assignee issue because you're trying to take up multiple major efforts where there're folks in community want to take anything up. You're also assigning yourself on SPARK-34198 which isn't even having a PR up for reviewing, right? Don't try to occupy major efforts in parallel and block others to even try out. was (Author: kabhwan): I'd say SPARK-10816 has no active progress so far because of lack of interest. Once you found the necessity then SPARK-10816 can be unblocked instead of spending another non-trivial time to reinvent the wheel, no? See SPARK-10816, there're SPIP docs, discussions, ideas around them, even perf tests on WIP PRs. These efforts were actually more than a month. What this issue provides? It's just a simple link Flink provides. No design doc, no implementation, no test. This JIRA issue basically does nothing yet. That said, it's far behind than the existing effort. You can't simply say existing PR is complicated than you have in mind unless you can prove it via similar sort of effort, SPIP doc with design doc. I pointed out JIRA issue assignee issue because you're trying to take up multiple major efforts where there're folks in community want to take anything up. You're also assigning yourself on SPARK-34198 which isn't even having a PR up for reviewing, right? Don't try to occupy major efforts in parallel. > 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