[jira] [Commented] (BEAM-10216) SESSION TVF Optimizations

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-10216:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> SESSION TVF Optimizations
> -------------------------
>
>                 Key: BEAM-10216
>                 URL: https://issues.apache.org/jira/browse/BEAM-10216
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql-zetasql
>            Reporter: Rui Wang
>            Priority: P2
>              Labels: stale-P2
>
> Current TVF Session has the following limitation:
> Use a "dummy" key to go through a GBK to compute window_start and window_end. This introduces an extra shuffle so it costs more.
> One optimizations we can do is always merge TableFunctionScanRel with AggregationRel (and also all Join Rel), thus we can use only one GBK to compute both SESSION window_start and window_end, and aggregations(joins).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)