Xiao Huang created FLINK-36463:
--
Summary: Disable some debezium options which do not take effect
Key: FLINK-36463
URL: https://issues.apache.org/jira/browse/FLINK-36463
Project: Flink
Issue Type
xuhuang created FLINK-36462:
---
Summary: Revert "remove per-job"
Key: FLINK-36462
URL: https://issues.apache.org/jira/browse/FLINK-36462
Project: Flink
Issue Type: Bug
Reporter: xuhuang
yux created FLINK-36461:
---
Summary: YAML job failed to schema evolve with unmatched transform
tables
Key: FLINK-36461
URL: https://issues.apache.org/jira/browse/FLINK-36461
Project: Flink
Issue Type: B
Sam Barker created FLINK-36460:
--
Summary: Refactor Kubernetes Operator Edge to Edge test setup
Key: FLINK-36460
URL: https://issues.apache.org/jira/browse/FLINK-36460
Project: Flink
Issue Type:
LvYanquan created FLINK-36459:
-
Summary: Add document to guide user to configure debezium
properties
Key: FLINK-36459
URL: https://issues.apache.org/jira/browse/FLINK-36459
Project: Flink
Issue
Thanks Junrui for the quick clarification!
Sounds good to me, +1 for this FLIP.
Best,
Rui
On Thu, Oct 10, 2024 at 10:52 AM Junrui Lee wrote:
> Hi Rui,
>
> Thank you for your response. Here are my replies to your questions:
>
> Regarding question 1: We plan to label the config options on the Fl
Hi Rui,
Thank you for your response. Here are my replies to your questions:
Regarding question 1: We plan to label the config options on the Flink
configuration page in the upcoming 2.0 version. In the long term, our goal
is to ensure that all config options visible to users are properly labeled.
He Wang created FLINK-36458:
---
Summary: Use original 'OceanBaseCEContainer' of testcontainers in
testing
Key: FLINK-36458
URL: https://issues.apache.org/jira/browse/FLINK-36458
Project: Flink
Issue
Thanks Junrui for driving this proposal!
It's valuable for users to distinguish all flink options.
I have 2 minor questions about this proposal:
1. Does this FLIP enrich the scope for all old flink options?
2. If the option is configured at the wrong level, could we
output some warn log to remind
Hello Ferenc. Sorry for the late response.
I think you are right and we should revert the FLINK-36310. We have already
supported the SQL job submission based on application mode several months
ago. I will write the design about this and reopen the FLIP-316 discussion
later. We hope Flink-2.0 suppo
Hi Ferenc,
Thanks for pointing this out! After confirmation with others, I think you
are right.
It's fair enough to revert the PR that remove per-job mode in
2.0-preview. But we need to make sure we don't include per-job stuff in
2.0.0.
Best regards,
Weijie
Ferenc Csaky 于2024年10月9日周三 21:55写道
Thanks Junrui for starting this discussion!
Prior to this, it takes some experience to correctly distinguish whether a
configuration item is effective at CLUSTER or JOB level, and this proposal
avoids such a burden.
And the FLIP looks good to me.
Best,
Yanquan
Zhu Zhu 于2024年10月9日周三 17:14写道：
>
Aleksandr Pilipenko created FLINK-36457:
---
Summary: Python DataStream API: calling add_jars or add_classpaths
results in corrupted execution config
Key: FLINK-36457
URL: https://issues.apache.org/jira/browse/
Hi Ferenc,
Thank you for creating this FLIP, having some kind of CLI deprecation
process would be very useful for developers and users. The FLIP does a good
job explaining the deprecation of actions, but there aren't any mentions of
command options. I think it would add some value to also include
Raul Garcia created FLINK-36456:
---
Summary: Improve Security in DatadogHttpReporterFactory by
providing ENV alternative to retrieve API key
Key: FLINK-36456
URL: https://issues.apache.org/jira/browse/FLINK-36456
Hello devs,
I just noticed there is an already merged change [1] that removes per-job mode
from the
codebase. Regarding that, I would like to mention FLINK-26000 [2] that exists
for the same
for quite a while, and the reason why we kept the code until now is that,
Application Mode
does not supp
Arvid Heise created FLINK-36455:
---
Summary: Sink should commit everything on notifyCheckpointCompleted
Key: FLINK-36455
URL: https://issues.apache.org/jira/browse/FLINK-36455
Project: Flink
Issu
Arvid Heise created FLINK-36454:
---
Summary: FlinkContainer always overwrites default config
Key: FLINK-36454
URL: https://issues.apache.org/jira/browse/FLINK-36454
Project: Flink
Issue Type: Bug
yux created FLINK-36453:
---
Summary: Backport DBZ-6502 patch to fix Oracle 23.x JDBC driver
compatbility
Key: FLINK-36453
URL: https://issues.apache.org/jira/browse/FLINK-36453
Project: Flink
Issue Type
LvYanquan created FLINK-36452:
-
Summary: Avoid EOFException when reading binlog after a large
table has just completed snapshot reading
Key: FLINK-36452
URL: https://issues.apache.org/jira/browse/FLINK-36452
xiechenling created FLINK-36451:
---
Summary: Kubernetes Application JobManager Potential Deadlock and
TaskManager Pod Residuals
Key: FLINK-36451
URL: https://issues.apache.org/jira/browse/FLINK-36451
Proj
Siddharth R created FLINK-36450:
---
Summary: Exclude log4j from curator-test
Key: FLINK-36450
URL: https://issues.apache.org/jira/browse/FLINK-36450
Project: Flink
Issue Type: Improvement
Siddharth R created FLINK-36449:
---
Summary: Bump apache-rat-plugin from 0.12 to 0.16.1
Key: FLINK-36449
URL: https://issues.apache.org/jira/browse/FLINK-36449
Project: Flink
Issue Type: Improvem
Kumar Mallikarjuna created FLINK-36448:
--
Summary: Compilation fails in IntelliJ
Key: FLINK-36448
URL: https://issues.apache.org/jira/browse/FLINK-36448
Project: Flink
Issue Type: Bug
Thanks Junrui for starting this discussion!
+1 for the proposal
Clarifying the scopes of config options can be beneficial for users.
Even Flink developers occasionally encounter confusion regarding the
scopes of various configurations, such as attempting to retrieve
job-specific settings from `Tas
25 matches
Mail list logo
