[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lincoln lee updated FLINK-23031:
Fix Version/s: (was: 1.19.0)
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: WenJun Min
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It brings overhead to the heap memory, especially for the job with large
> scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lincoln lee updated FLINK-23031:
Fix Version/s: 1.20.0
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: WenJun Min
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0, 1.20.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It brings overhead to the heap memory, especially for the job with large
> scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-23031:
Fix Version/s: 1.19.0
(was: 1.18.0)
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It brings overhead to the heap memory, especially for the job with large
> scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-23031:
-
Fix Version/s: 1.18.0
(was: 1.17.0)
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It brings overhead to the heap memory, especially for the job with large
> scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xingbo Huang updated FLINK-23031:
-
Fix Version/s: 1.17.0
(was: 1.16.0)
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It brings overhead to the heap memory, especially for the job with large
> scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Gao updated FLINK-23031:
Fix Version/s: 1.16.0
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0, 1.16.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It brings overhead to the heap memory, especially for the job with large
> scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-23031:
---
Description:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two drawback:
1. It brings overhead to the heap memory, especially for the job with large
scale number of group by key
2. The same result will be compute repeatedly , but not deliver by Window
Operator. It's somehow meaningless work.
We can simply avoid to register next timer in {{onProcessingTime}} phase to
optimize the performance. Due to the Window Operator already eliminate the same
output, So this change will not
cause compatible problem
was:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two drawback:
1. It will bring overhead to the heap memory, especially for the job with large
scale number of group by key
2. The same result will be compute repeatedly , but not deliver by Window
Operator. It's somehow meaningless work.
We can simply avoid to register next timer in {{onProcessingTime}} phase to
optimize the performance. Due to the Window Operator already eliminate the same
output, So this change will not
cause compatible problem
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It brings overhead to the heap memory, especially for the job with large
> scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-23031:
---
Description:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two drawback:
1. It will bring overhead to the heap memory, especially for the job with large
scale number of group by key
2. The same result will be compute repeatedly , but not deliver by Window
Operator. It's somehow meaningless work.
We can simply avoid to register next timer in {{onProcessingTime}} phase to
optimize the performance. Due to the Window Operator already eliminate the same
output, So this change will not
cause compatible problem
was:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two drawback
1. It will bring overhead to the heap memory, especially for the job with large
scale number of group by key
2. The same result will be compute repeatedly , but not deliver by Window
Operator. It's somehow meaningless work.
We can simply avoid to register next timer in {{onProcessingTime}} phase to
optimize the performance. Due to the Window Operator already eliminate the same
output, So this change will not
cause compatible problem
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback:
> 1. It will bring overhead to the heap memory, especially for the job with
> large scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-23031:
---
Description:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two drawback
1. It will bring overhead to the heap memory, especially for the job with large
scale number of group by key
2. The same result will be compute repeatedly , but not deliver by Window
Operator. It's somehow meaningless work.
We can simply avoid to register next timer in {{onProcessingTime}} phase to
optimize the performance. Due to the Window Operator already eliminate the same
output, So this change will not
cause compatible problem
was:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two drawback
1. It will bring overhead to the heap memory, especially for the job with large
scale number of group by key
2. The same result will be compute repeatedly , but not deliver by Window
Operator. It's somehow meaningless work.
We can simply avoid to register next timer in {{onProcessingTime}} phase to
optimize the performance. Due to the Window Operator already
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback
> 1. It will bring overhead to the heap memory, especially for the job with
> large scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already eliminate the
> same output, So this change will not
> cause compatible problem
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[
https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-23031:
---
Description:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two drawback
1. It will bring overhead to the heap memory, especially for the job with large
scale number of group by key
2. The same result will be compute repeatedly , but not deliver by Window
Operator. It's somehow meaningless work.
We can simply avoid to register next timer in {{onProcessingTime}} phase to
optimize the performance. Due to the Window Operator already
was:
Currently, Flink support early trigger for Window Operator, But it will trigger
periodically after the first element in. This come up with two
1.
> Support to emit window result with periodic or non_periodic
> ---
>
> Key: FLINK-23031
> URL: https://issues.apache.org/jira/browse/FLINK-23031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
>Reporter: Aitozi
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Currently, Flink support early trigger for Window Operator, But it will
> trigger periodically after the first element in. This come up with two
> drawback
> 1. It will bring overhead to the heap memory, especially for the job with
> large scale number of group by key
> 2. The same result will be compute repeatedly , but not deliver by Window
> Operator. It's somehow meaningless work.
> We can simply avoid to register next timer in {{onProcessingTime}} phase to
> optimize the performance. Due to the Window Operator already
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-23031: --- Description: Currently, Flink support early trigger for Window Operator, But it will trigger periodically after the first element in. This come up with two 1. > Support to emit window result with periodic or non_periodic > --- > > Key: FLINK-23031 > URL: https://issues.apache.org/jira/browse/FLINK-23031 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Aitozi >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Currently, Flink support early trigger for Window Operator, But it will > trigger periodically after the first element in. This come up with two > 1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-23031: --- Fix Version/s: 1.15.0 > Support to emit window result with periodic or non_periodic > --- > > Key: FLINK-23031 > URL: https://issues.apache.org/jira/browse/FLINK-23031 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Aitozi >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23031) Support to emit window result with periodic or non_periodic
[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-23031: --- Labels: pull-request-available (was: ) > Support to emit window result with periodic or non_periodic > --- > > Key: FLINK-23031 > URL: https://issues.apache.org/jira/browse/FLINK-23031 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Aitozi >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
