[
https://issues.apache.org/jira/browse/FLINK-28751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28751:
---
Description:
When I use the JSON_VALUE function, I found the performance is very poor. It's
mainly
Aitozi created FLINK-28751:
--
Summary: Poor performance of the built in json_value function
Key: FLINK-28751
URL: https://issues.apache.org/jira/browse/FLINK-28751
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-27576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17571152#comment-17571152
]
Aitozi commented on FLINK-27576:
Hi [~zhisheng], I think this problem have been fixed via
[
https://issues.apache.org/jira/browse/FLINK-28531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566188#comment-17566188
]
Aitozi commented on FLINK-28531:
[~xtsong] Thanks for your information. It seems a duplicated issue :).
[
https://issues.apache.org/jira/browse/FLINK-28531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566124#comment-17566124
]
Aitozi commented on FLINK-28531:
cc [~wangyang0918] [~xtsong]
> Shutdown cluster after history server
[
https://issues.apache.org/jira/browse/FLINK-28531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566123#comment-17566123
]
Aitozi commented on FLINK-28531:
I propose to fix this in two way:
First, in the Dispatcher, we also
Aitozi created FLINK-28531:
--
Summary: Shutdown cluster after history server archive finished
Key: FLINK-28531
URL: https://issues.apache.org/jira/browse/FLINK-28531
Project: Flink
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FLINK-28477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi closed FLINK-28477.
--
Resolution: Won't Fix
> Support to scan the history server dir with max depth
>
[
https://issues.apache.org/jira/browse/FLINK-28477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564777#comment-17564777
]
Aitozi commented on FLINK-28477:
Got it, closed.
> Support to scan the history server dir with max
[
https://issues.apache.org/jira/browse/FLINK-28478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28478:
---
Description:
When I test case with https://issues.apache.org/jira/browse/FLINK-28187
I hit that the
[
https://issues.apache.org/jira/browse/FLINK-28478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564641#comment-17564641
]
Aitozi commented on FLINK-28478:
cc [~gyfora]
> Session Cluster will lost if it failed between status
[
https://issues.apache.org/jira/browse/FLINK-28478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28478:
---
Description:
When I test case with https://issues.apache.org/jira/browse/FLINK-28187
I hit that the
[
https://issues.apache.org/jira/browse/FLINK-28478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28478:
---
Description:
When I test case with https://issues.apache.org/jira/browse/FLINK-28187
I found that the
Aitozi created FLINK-28478:
--
Summary: Session Cluster will lost if it failed between status
recorded and deploy
Key: FLINK-28478
URL: https://issues.apache.org/jira/browse/FLINK-28478
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564637#comment-17564637
]
Aitozi commented on FLINK-28187:
[~gyfora] Thanks for your hint, I take a look on it
> Duplicate job
[
https://issues.apache.org/jira/browse/FLINK-28477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28477:
---
Description:
In the {{HistoryServerArchiveFetcher}}, we only list the archives specified by
the
[
https://issues.apache.org/jira/browse/FLINK-28477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28477:
---
Description:
In the {{HistoryServerArchiveFetcher}}, we only list the archives specified by
the
[
https://issues.apache.org/jira/browse/FLINK-28477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564636#comment-17564636
]
Aitozi commented on FLINK-28477:
cc [~guoyangze] [~xtsong]
> Support to scan the history server dir
[
https://issues.apache.org/jira/browse/FLINK-28477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28477:
---
Issue Type: Improvement (was: Bug)
> Support to scan the history server dir with max depth
>
Aitozi created FLINK-28477:
--
Summary: Support to scan the history server dir with max depth
Key: FLINK-28477
URL: https://issues.apache.org/jira/browse/FLINK-28477
Project: Flink
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17559170#comment-17559170
]
Aitozi commented on FLINK-28187:
FYI, I'm working on this now, please help assign the ticket [~gyfora]
[
https://issues.apache.org/jira/browse/FLINK-27979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17559169#comment-17559169
]
Aitozi commented on FLINK-27979:
This issue is mean to support the upgrade session cluster in a more
[
https://issues.apache.org/jira/browse/FLINK-27921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557982#comment-17557982
]
Aitozi commented on FLINK-27921:
I think the reason behind here may be the affected benchmark will run
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557837#comment-17557837
]
Aitozi commented on FLINK-28187:
OK, I will work on it in this way
> Duplicate job submission for
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557828#comment-17557828
]
Aitozi commented on FLINK-28187:
I think it over again the generation will make check whether the
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557824#comment-17557824
]
Aitozi commented on FLINK-28187:
> For sessionjobs we need to cover both using the jobid magic somehow
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557782#comment-17557782
]
Aitozi commented on FLINK-28187:
[~gyfora] I add one comment here:
[
https://issues.apache.org/jira/browse/FLINK-28207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557763#comment-17557763
]
Aitozi commented on FLINK-28207:
The option is introduced to let user can choose to enable/disable the
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557518#comment-17557518
]
Aitozi commented on FLINK-28187:
IMO, there is one and only one job for one FlinkSessionJob, so I think
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557513#comment-17557513
]
Aitozi edited comment on FLINK-28187 at 6/22/22 3:19 PM:
-
I'm afraid of not
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557513#comment-17557513
]
Aitozi edited comment on FLINK-28187 at 6/22/22 3:16 PM:
-
I'm afraid of not
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557513#comment-17557513
]
Aitozi commented on FLINK-28187:
I'm afraid of not clearly expressing my meaning. I will try to give an
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557404#comment-17557404
]
Aitozi commented on FLINK-28187:
I get your meaning now, but I think the case is a bit different from
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557387#comment-17557387
]
Aitozi commented on FLINK-28187:
thanks, I will check it now
> Duplicate job submission for
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557379#comment-17557379
]
Aitozi edited comment on FLINK-28187 at 6/22/22 11:26 AM:
--
Currently, it
[
https://issues.apache.org/jira/browse/FLINK-28187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557379#comment-17557379
]
Aitozi commented on FLINK-28187:
Yes, I generate the JobId in advance to help duplicate the job
[
https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553414#comment-17553414
]
Aitozi commented on FLINK-27925:
Get your meaning, I will try to test for it
> Avoid to create watcher
[
https://issues.apache.org/jira/browse/FLINK-28008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553408#comment-17553408
]
Aitozi commented on FLINK-28008:
I think so, but I have not make sure
> Can not get secondary resource
[
https://issues.apache.org/jira/browse/FLINK-28012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553407#comment-17553407
]
Aitozi commented on FLINK-28012:
[~haoxin] there is a link to the flink filesystem now, you could refer
[
https://issues.apache.org/jira/browse/FLINK-27862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553406#comment-17553406
]
Aitozi commented on FLINK-27862:
Hi [~xtsong] , I have an offline discussion with [~Weijie Guo]. And I
[
https://issues.apache.org/jira/browse/FLINK-28012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553249#comment-17553249
]
Aitozi commented on FLINK-28012:
I think the gcs should work with the filesystem based fetcher, have you
[
https://issues.apache.org/jira/browse/FLINK-28008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553018#comment-17553018
]
Aitozi commented on FLINK-28008:
I don't know if there any trick with the new sdk version. cc
[
https://issues.apache.org/jira/browse/FLINK-28008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553014#comment-17553014
]
Aitozi commented on FLINK-28008:
I test with the last release version with
{code:java}
helm install
[
https://issues.apache.org/jira/browse/FLINK-28008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553014#comment-17553014
]
Aitozi edited comment on FLINK-28008 at 6/11/22 3:01 AM:
-
I test with the last
[
https://issues.apache.org/jira/browse/FLINK-28008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28008:
---
Summary: Can not get secondary resource from context after operator restart
(was: Can not get secondary
[
https://issues.apache.org/jira/browse/FLINK-28008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-28008:
---
Description:
how to reproduce:
* create session and submit session job
* delete session job
* restart
Aitozi created FLINK-28008:
--
Summary: Can not get secondary resource from after operator restart
Key: FLINK-28008
URL: https://issues.apache.org/jira/browse/FLINK-28008
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552554#comment-17552554
]
Aitozi edited comment on FLINK-27925 at 6/10/22 5:14 AM:
-
I think it will only
[
https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552554#comment-17552554
]
Aitozi commented on FLINK-27925:
Will it cache extra pods of other jobs if we specify the current job
Aitozi created FLINK-27979:
--
Summary: Support to upgrade session cluster in a more fine grained
way
Key: FLINK-27979
URL: https://issues.apache.org/jira/browse/FLINK-27979
Project: Flink
Issue
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552253#comment-17552253
]
Aitozi commented on FLINK-27960:
For convenient, I think we could include it in the main branch like the
[
https://issues.apache.org/jira/browse/FLINK-27273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552240#comment-17552240
]
Aitozi commented on FLINK-27273:
I think it's a valid concern. But we could support other case first. I
[
https://issues.apache.org/jira/browse/FLINK-27273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552240#comment-17552240
]
Aitozi edited comment on FLINK-27273 at 6/9/22 2:09 PM:
I think it's a valid
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552221#comment-17552221
]
Aitozi commented on FLINK-27960:
Maybe it's due to the network limit
> Make the apt-get updating
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552219#comment-17552219
]
Aitozi commented on FLINK-27960:
>From my log it don't finish in 8min, I do not know the root cause. If
[
https://issues.apache.org/jira/browse/FLINK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551864#comment-17551864
]
Aitozi commented on FLINK-26493:
[~gyfora] I have not invest time to start this work, but I still think
[
https://issues.apache.org/jira/browse/FLINK-27273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551661#comment-17551661
]
Aitozi commented on FLINK-27273:
What do you think of this cc [~gyfora] [~wangyang0918]
> Support both
[
https://issues.apache.org/jira/browse/FLINK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-26493:
---
Component/s: Kubernetes Operator
> Use state machine based mechanism to simply the reconciler
>
Aitozi created FLINK-27961:
--
Summary: The EventUtils generate event name should take the
resource's uid into account
Key: FLINK-27961
URL: https://issues.apache.org/jira/browse/FLINK-27961
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27960:
---
Attachment: screenshot-1.png
> Make the apt-get updating optional
> ---
>
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27960:
---
Attachment: (was: image-2022-06-08-22-06-44-586.png)
> Make the apt-get updating optional
>
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27960:
---
Description:
I notice that it cost much time to do the apt-get updating, it's not necessary
during
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27960:
---
Description:
I notice that it cost much time to do the apt-get updating, it's not necessary
during
[
https://issues.apache.org/jira/browse/FLINK-27960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27960:
---
Attachment: image-2022-06-08-22-06-44-586.png
> Make the apt-get updating optional
>
Aitozi created FLINK-27960:
--
Summary: Make the apt-get updating optional
Key: FLINK-27960
URL: https://issues.apache.org/jira/browse/FLINK-27960
Project: Flink
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi closed FLINK-27930.
--
Resolution: Won't Fix
> Format the timestamp in status to make it readable
>
[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550872#comment-17550872
]
Aitozi commented on FLINK-27930:
Get it
> Format the timestamp in status to make it readable
>
[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550844#comment-17550844
]
Aitozi edited comment on FLINK-27930 at 6/7/22 7:24 AM:
It's in string type now,
[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550844#comment-17550844
]
Aitozi commented on FLINK-27930:
It's in string type now, but store the unix timestamp value. Will this
[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27930:
---
Description:
Currently, the timestamp in status show the unix timestamp, I think we could
improve it to an
[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27930:
---
Summary: Format the timestamp in status to make it readable (was: Format
the timestamp in status to make
[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27930:
---
Description:
Currently, the timestamp in status show the unix timestamp, I think we could
improve it to a
Aitozi created FLINK-27930:
--
Summary: Format the timestamp in status to make it explicit
Key: FLINK-27930
URL: https://issues.apache.org/jira/browse/FLINK-27930
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-27862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550832#comment-17550832
]
Aitozi commented on FLINK-27862:
Thanks [~Weijie Guo] , [~xtsong] for your kindness guide, I will take a
[
https://issues.apache.org/jira/browse/FLINK-27497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550799#comment-17550799
]
Aitozi commented on FLINK-27497:
continue this work now
> Track terminal job states in the observer
>
[
https://issues.apache.org/jira/browse/FLINK-27921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27921:
---
Description:
As discussed in
[https://github.com/apache/flink/pull/19840#discussion_r884242067] .This
[
https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550749#comment-17550749
]
Aitozi commented on FLINK-27925:
cc [~wangyang0918]
> Avoid to create watcher without the
[
https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27925:
---
Description:
Currently, we create the watcher in KubernetesResourceManager. But it do not
pass the
Aitozi created FLINK-27925:
--
Summary: Avoid to create watcher without the resourceVersion
Key: FLINK-27925
URL: https://issues.apache.org/jira/browse/FLINK-27925
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-27868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550716#comment-17550716
]
Aitozi commented on FLINK-27868:
I think it will be a good improvement to savepoint with the work of
[
https://issues.apache.org/jira/browse/FLINK-27862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550507#comment-17550507
]
Aitozi commented on FLINK-27862:
Hi [~Weijie Guo] Thanks for starting this work. I'm interested in this
Aitozi created FLINK-27921:
--
Summary: Introduce the checkResourceRequirementsWithDelay in
DeclarativeSlotManager
Key: FLINK-27921
URL: https://issues.apache.org/jira/browse/FLINK-27921
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-27821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542961#comment-17542961
]
Aitozi commented on FLINK-27821:
[~Miuler] The deletion of the session cluster's flinkdeployment object
[
https://issues.apache.org/jira/browse/FLINK-27737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540781#comment-17540781
]
Aitozi commented on FLINK-27737:
Yes, I'd like to work on this.
> Remove legacy support for unfenced
Aitozi created FLINK-27737:
--
Summary: Clean the outdated comments and unfencedMainExecutor
Key: FLINK-27737
URL: https://issues.apache.org/jira/browse/FLINK-27737
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-27576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540608#comment-17540608
]
Aitozi commented on FLINK-27576:
Hi [~zhisheng] I have opened a PR for this, please let me know if you
[
https://issues.apache.org/jira/browse/FLINK-27666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538567#comment-17538567
]
Aitozi commented on FLINK-27666:
I could work on this. please assign this to me, I will try to push a
[
https://issues.apache.org/jira/browse/FLINK-27576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537871#comment-17537871
]
Aitozi commented on FLINK-27576:
I have not started, I will prepare the PR this week.
> Flink will
[
https://issues.apache.org/jira/browse/FLINK-27497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537304#comment-17537304
]
Aitozi commented on FLINK-27497:
[~gyfora] Thanks for your remind.
Besides I have question when I test
[
https://issues.apache.org/jira/browse/FLINK-27613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537177#comment-17537177
]
Aitozi commented on FLINK-27613:
Yes, especially when we have to do operation on all the jobs of a
[
https://issues.apache.org/jira/browse/FLINK-27497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537140#comment-17537140
]
Aitozi commented on FLINK-27497:
working on this now
> Track terminal job states in the observer
>
[
https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537136#comment-17537136
]
Aitozi commented on FLINK-17232:
I have pushed a PR to remove the implicit behavior to fallback to
[
https://issues.apache.org/jira/browse/FLINK-27615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537011#comment-17537011
]
Aitozi edited comment on FLINK-27615 at 5/14/22 10:12 AM:
--
what about
[
https://issues.apache.org/jira/browse/FLINK-27615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537011#comment-17537011
]
Aitozi commented on FLINK-27615:
what about supporting user to define their own namespace selector
[
https://issues.apache.org/jira/browse/FLINK-27613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27613:
---
Description: The custorm resource do not supported list by field selector,
So I think add a label to get
Aitozi created FLINK-27614:
--
Summary: Use informer in webhook to avoid query apiserver at each
update
Key: FLINK-27614
URL: https://issues.apache.org/jira/browse/FLINK-27614
Project: Flink
Issue
[
https://issues.apache.org/jira/browse/FLINK-26784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536992#comment-17536992
]
Aitozi commented on FLINK-26784:
The {{{}FlinkSessionJob{}}}'s functionality are basically completed.
[
https://issues.apache.org/jira/browse/FLINK-26784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536992#comment-17536992
]
Aitozi edited comment on FLINK-26784 at 5/14/22 8:21 AM:
-
The
Aitozi created FLINK-27613:
--
Summary: Add label for the session job to help list the session
jobs in the same session cluster
Key: FLINK-27613
URL: https://issues.apache.org/jira/browse/FLINK-27613
Project:
[
https://issues.apache.org/jira/browse/FLINK-27612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-27612:
---
Parent: FLINK-26784
Issue Type: Sub-task (was: Improvement)
> Generate waring events when deleting
201 - 300 of 803 matches
Mail list logo
