Zezheng Qin created FLINK-20556:
---
Summary: org.apache.flink.api.common.InvalidProgramException:
Table program cannot be compiled. This is a bug. Please file an issue.
Key: FLINK-20556
URL: https://issues.apache.org
DaiXinyu created FLINK-20555:
Summary: 404 url dependency error in Flink Website
Key: FLINK-20555
URL: https://issues.apache.org/jira/browse/FLINK-20555
Project: Flink
Issue Type: New Feature
ming li created FLINK-20554:
---
Summary: The Checkpointed Data Size of the Latest Completed
Checkpoint is incorrectly displayed on the Overview page of the UI
Key: FLINK-20554
URL: https://issues.apache.org/jira/browse/FL
Qingsheng Ren created FLINK-20553:
-
Summary: Add end-to-end test case for new Kafka source
Key: FLINK-20553
URL: https://issues.apache.org/jira/browse/FLINK-20553
Project: Flink
Issue Type: I
mei jie created FLINK-20552:
---
Summary: Jdbc connector don't sink buffer data when checkpoint
Key: FLINK-20552
URL: https://issues.apache.org/jira/browse/FLINK-20552
Project: Flink
Issue Type: Bug
Hi devs,
So far we keep developing the native K8s integration for three major
release cycles in Flink.
-
Flink 1.10
-
Beta version
-
Dynamic resource allocation
-
Session mode only
-
Flink 1.11
-
Application mode
-
Usabil
Great. Easiest discussion thread ever.
https://issues.apache.org/jira/browse/FLINK-20551
On Wed, Dec 9, 2020 at 6:55 AM Wei Zhong wrote:
> +1
>
> This is a very good proposal. The Python Table API documentation also
> contains some code that still uses the old planner. We may need to do the
> s
Seth Wiesman created FLINK-20551:
Summary: Make SQL documentation Blink only
Key: FLINK-20551
URL: https://issues.apache.org/jira/browse/FLINK-20551
Project: Flink
Issue Type: Improvement
Han created FLINK-20550:
---
Summary: Wrong savepoint config in some docs
Key: FLINK-20550
URL: https://issues.apache.org/jira/browse/FLINK-20550
Project: Flink
Issue Type: Improvement
Component
Rui Li created FLINK-20549:
--
Summary: New ExecutionContext doesn't inherit classloader from
previous context
Key: FLINK-20549
URL: https://issues.apache.org/jira/browse/FLINK-20549
Project: Flink
I
+1
This is a very good proposal. The Python Table API documentation also contains
some code that still uses the old planner. We may need to do the same for the
Python Table API documentation in the future.
Best,
Wei
> 在 2020年12月9日,12:35,Jark Wu 写道:
>
> +1
>
> This is a very good idea.
>
>
Roman Khachatryan created FLINK-20548:
-
Summary: Provide an option to disable propagation of timed out
barriers
Key: FLINK-20548
URL: https://issues.apache.org/jira/browse/FLINK-20548
Project: Fli
Actually, I think the key point is that the Flink client is not friendly to
the deployers.
Most companies have their own deployers and I believe many of them depend on
the cli commands(e.g. "flink run/run-application").
I am not sure whether using the rest cluster client is the best choice. But
we
Zhilong Hong created FLINK-20547:
Summary: Batch job fails due to the exception in network stack
Key: FLINK-20547
URL: https://issues.apache.org/jira/browse/FLINK-20547
Project: Flink
Issue T
zoucao created FLINK-20546:
--
Summary: Misuse of the method in KafkaDynamicTableFactoryTest
Key: FLINK-20546
URL: https://issues.apache.org/jira/browse/FLINK-20546
Project: Flink
Issue Type: Improvem
15 matches
Mail list logo