Gabor Somogyi created FLINK-36173:
-
Summary: Invalid link in checkpoint documentation
Key: FLINK-36173
URL: https://issues.apache.org/jira/browse/FLINK-36173
Project: Flink
Issue Type: Bug
Hi All,
I'm glad to announce that FLIP-474[1] has been accepted.
There are 9 approving votes, 7 of which are binding:
- Marton Balassi (binding)
- Ferenc Csaky (binding)
- Gyula Fora (binding)
- Orhidi Matyas (binding)
- Peter Huang (non-binding)
- Clara Xiong (non-binding)
- Zakelly Lan (binding
Hongshun Wang created FLINK-36174:
-
Summary: CDC yaml without pipeline will throw NullPointException
Key: FLINK-36174
URL: https://issues.apache.org/jira/browse/FLINK-36174
Project: Flink
Iss
xuyang created FLINK-36175:
--
Summary: Remove `register_table_source` and `register_table_sink`
in python module
Key: FLINK-36175
URL: https://issues.apache.org/jira/browse/FLINK-36175
Project: Flink
Arvid Heise created FLINK-36176:
---
Summary: Remove support for ancient Kafka versions
Key: FLINK-36176
URL: https://issues.apache.org/jira/browse/FLINK-36176
Project: Flink
Issue Type: Technical
Hi everyone,
for the 2.0 work, we are expecting to run into public API changes quite a
bit. This would get picked up by the japicmp plugin. The usual way is to
add exclusions to the plugin configuration [1] generating a (presumably
long) list of API changes.
I'm wondering whether we, instead, woul
Arvid Heise created FLINK-36177:
---
Summary: Deprecating KafkaShuffle
Key: FLINK-36177
URL: https://issues.apache.org/jira/browse/FLINK-36177
Project: Flink
Issue Type: Technical Debt
C
Hi Matthias,
I would turn japicmp for 2.0 off because adding a long list of exceptions
doesn't give any value.
1.x and 2.x is not going to be compatible in any way and when 2.x released,
then that will be the new
japicmp baseline (after a heavy migration).
What I see as a potential risk it that w
LvYanquan created FLINK-36178:
-
Summary: Parse CREATE TABLE LIKE to CreateTableEvent
Key: FLINK-36178
URL: https://issues.apache.org/jira/browse/FLINK-36178
Project: Flink
Issue Type: Improvement
Siddharth R created FLINK-36179:
---
Summary: Bump log4j version
Key: FLINK-36179
URL: https://issues.apache.org/jira/browse/FLINK-36179
Project: Flink
Issue Type: Improvement
Components
Wenbing Shen created FLINK-36180:
Summary: Flink pulsar connector when restoring from the state, the
unconsumed messages of the first batch will be lost
Key: FLINK-36180
URL: https://issues.apache.org/jira/browse/
Thanks for bringing up this! It would be a useful feature for batch users.
For the FLIP, I have some questions:
1st, the implementation plan is to rewrite the optimization based on the
execnode of the table planner, but the config option for the optimization
is under flink-core module, does it me
Martijn Visser created FLINK-36181:
--
Summary: Drop support for Java 8 and use Java 17 by default
Key: FLINK-36181
URL: https://issues.apache.org/jira/browse/FLINK-36181
Project: Flink
Issue
EMERSON WANG created FLINK-36182:
Summary: PyFlink SQL Job Got IllegalStateException During Task
Manager Shutdown
Key: FLINK-36182
URL: https://issues.apache.org/jira/browse/FLINK-36182
Project: Flink
yux created FLINK-36183:
---
Summary: Lenient mode doesn't work with route blocks
Key: FLINK-36183
URL: https://issues.apache.org/jira/browse/FLINK-36183
Project: Flink
Issue Type: Bug
Component
yux created FLINK-36184:
---
Summary: Transform Operator swallows schema changes from tables
not present in transform rules
Key: FLINK-36184
URL: https://issues.apache.org/jira/browse/FLINK-36184
Project: Flink
Junrui Li created FLINK-36185:
-
Summary: Remove RuntimeContext#getExecutionConfig
Key: FLINK-36185
URL: https://issues.apache.org/jira/browse/FLINK-36185
Project: Flink
Issue Type: Sub-task
Yue Ma created FLINK-36186:
--
Summary: Speed up RocksDB close during manual compaction
Key: FLINK-36186
URL: https://issues.apache.org/jira/browse/FLINK-36186
Project: Flink
Issue Type: Bug
Hi Lincoln Lee,
Thanks for your feedback!
For the 1st question, thank you for the reminder. This optimization is only
available for Table jobs in batch mode, and I have put these new options
into table module. I also replaced the "enable" and "force" configurations
with a new enum type configuratio
19 matches
Mail list logo