[
https://issues.apache.org/jira/browse/FLINK-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770818#comment-17770818
]
Gabor Somogyi commented on FLINK-33155:
---
The fact that YARN is not able to renew t
[
https://issues.apache.org/jira/browse/FLINK-26586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770815#comment-17770815
]
Rui Fan commented on FLINK-26586:
-
Thanks [~masteryhx] [~Matthias Schwalbe] for discuss
1996fanrui commented on code in PR #677:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/677#discussion_r1342082710
##
flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/reconciler/deployment/AbstractFlinkResourceReconciler.java:
##
@@ -1
xiangyuf commented on PR #23201:
URL: https://github.com/apache/flink/pull/23201#issuecomment-1741939759
> Thanks for the PR, Xiangyu! I give it a first pass and left some comments.
>
> My major concern is that, place the resource allocation decisions related
to the minimum resources
[
https://issues.apache.org/jira/browse/FLINK-31825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31825:
---
Labels: auto-deprioritized-major test-stability (was: stale-major
test-stability)
Pri
[
https://issues.apache.org/jira/browse/FLINK-32722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-32722:
---
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://g
[
https://issues.apache.org/jira/browse/FLINK-29390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-29390:
---
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink
[
https://issues.apache.org/jira/browse/FLINK-32665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-32665:
---
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Ji
[
https://issues.apache.org/jira/browse/FLINK-28440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28440:
---
Labels: auto-deprioritized-critical pull-request-available stale-assigned
test-stability (w
[
https://issues.apache.org/jira/browse/FLINK-32910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-32910:
---
Labels: pull-request-available stale-assigned starter (was:
pull-request-available starter)
[
https://issues.apache.org/jira/browse/FLINK-33007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-33007:
---
Labels: pull-request-available (was: )
> Integrate autoscaler config validation into the ge
srpraneeth opened a new pull request, #682:
URL: https://github.com/apache/flink-kubernetes-operator/pull/682
## What is the purpose of the change
*Currently the AutoScaler configurations are not validated, hence they fail
at runtime. This change intends to introduce a validator plugi
gaborgsomogyi commented on PR #23479:
URL: https://github.com/apache/flink/pull/23479#issuecomment-1741815889
cc @gyfora @mbalassi
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific co
[
https://issues.apache.org/jira/browse/FLINK-33173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tanjialiang updated FLINK-33173:
Description: In the connector specifications of
[FLIP-33|https://cwiki.apache.org/confluence/displ
[
https://issues.apache.org/jira/browse/FLINK-33173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-33173:
---
Labels: pull-request-available (was: )
> Support currentFetchEventTimeLag metrics for Kafka
[
https://issues.apache.org/jira/browse/FLINK-33173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tanjialiang updated FLINK-33173:
Component/s: Connectors / Kafka
> Support currentFetchEventTimeLag metrics for KafkaSource
> -
Tan-JiaLiang opened a new pull request, #54:
URL: https://github.com/apache/flink-connector-kafka/pull/54
## What is the purpose of the change
In the connector specifications of
[FLIP-33](https://cwiki.apache.org/confluence/display/FLINK/FLIP-33),
`currentFetchEventTimeLag` m
mateczagany commented on code in PR #677:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/677#discussion_r1341955135
##
flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/reconciler/deployment/AbstractFlinkResourceReconciler.java:
##
@@ -
[
https://issues.apache.org/jira/browse/FLINK-33173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tanjialiang updated FLINK-33173:
Description: In the connector specifications of
[FLIP-33|https://cwiki.apache.org/confluence/displ
[
https://issues.apache.org/jira/browse/FLINK-33173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tanjialiang updated FLINK-33173:
Description: In the connector specifications of
[FLIP-33|https://cwiki.apache.org/confluence/displ
tanjialiang created FLINK-33173:
---
Summary: Support currentFetchEventTimeLag metrics for KafkaSource
Key: FLINK-33173
URL: https://issues.apache.org/jira/browse/FLINK-33173
Project: Flink
Issue
flinkbot commented on PR #23479:
URL: https://github.com/apache/flink/pull/23479#issuecomment-1741757469
## CI report:
* 996155450e0a34edfca7ce79f3c2363a3c075c43 UNKNOWN
Bot commands
The @flinkbot bot supports the following commands:
- `@flinkbot run azure`
[
https://issues.apache.org/jira/browse/FLINK-33172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-33172:
---
Labels: pull-request-available (was: )
> Bump numpy version
> --
>
>
gaborgsomogyi opened a new pull request, #23479:
URL: https://github.com/apache/flink/pull/23479
## What is the purpose of the change
`Numpy 1.21.4` was released on Nov 5, 2021 which is quite old. In this PR
I've bumped it to `1.22.4`.
## Brief change log
Bumped numpy ve
[
https://issues.apache.org/jira/browse/FLINK-32223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770703#comment-17770703
]
Gabor Somogyi commented on FLINK-32223:
---
I've just double checked and before this
[
https://issues.apache.org/jira/browse/FLINK-33172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Somogyi reassigned FLINK-33172:
-
Assignee: Gabor Somogyi
> Bump numpy version
> --
>
> K
Gabor Somogyi created FLINK-33172:
-
Summary: Bump numpy version
Key: FLINK-33172
URL: https://issues.apache.org/jira/browse/FLINK-33172
Project: Flink
Issue Type: Improvement
Compon
[
https://issues.apache.org/jira/browse/FLINK-33171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770698#comment-17770698
]
Feng Jiajie commented on FLINK-33171:
-
I have attempted to submit a pull request:
[
flinkbot commented on PR #23478:
URL: https://github.com/apache/flink/pull/23478#issuecomment-1741746512
## CI report:
* 296673ca23b3cc4cbbead7cccf5d70c5d85a9740 UNKNOWN
Bot commands
The @flinkbot bot supports the following commands:
- `@flinkbot run azure`
[
https://issues.apache.org/jira/browse/FLINK-33171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-33171:
---
Labels: pull-request-available (was: )
> Table SQL support Not Equal for TimePoint type and
fengjiajie opened a new pull request, #23478:
URL: https://github.com/apache/flink/pull/23478
## What is the purpose of the change
When executing the following SQL:
SELECT
time1,
time1 = '2023-09-30 18:22:42.123' AS eq1,
NOT (time1 = '2023-09-30 18:2
Feng Jiajie created FLINK-33171:
---
Summary: Table SQL support Not Equal for TimePoint type and
TimeString
Key: FLINK-33171
URL: https://issues.apache.org/jira/browse/FLINK-33171
Project: Flink
Tan-JiaLiang commented on PR #52:
URL:
https://github.com/apache/flink-connector-kafka/pull/52#issuecomment-1741714161
@tzulitai Sorry for late.
In your example, all of partitions's `currentOffset` is -1 at tp=1 before
this PR changes. After this PR changes, all the partitions's `curren
[
https://issues.apache.org/jira/browse/FLINK-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770648#comment-17770648
]
袁枫 edited comment on FLINK-33155 at 9/30/23 7:25 AM:
-
The root cause
34 matches
Mail list logo