Chesnay Schepler created FLINK-21510:
Summary: ExecutionGraph metrics collide on restart
Key: FLINK-21510
URL: https://issues.apache.org/jira/browse/FLINK-21510
Project: Flink
Issue
Wei Zhong created FLINK-21509:
-
Summary: "w.start" returns "1970-01-01" when used with Pandas UDAF
after grouping by slide window with processing time
Key: FLINK-21509
URL:
Hi Timo,
First of all I want to thank you for introducing this planner design back
in 1.9, this is a great work
that allows lots of blink features to be merged to Flink in a reasonably
short time. It greatly
accelerates the evolution speed of Table & SQL.
Everything comes with a cost, as you
Hi Yun,
The termination phase I drafted depends on a de-fact that
`notifyCheckpointComplete` is ignored currently after `close`. Thus, any
external materialization inside `close`(including `endInput`) or
`notifyCheckpointComplete` is either not guaranteed or not committed.
I tried to emphasize
Guowei Ma created FLINK-21508:
-
Summary: CollectITCase hangs
Key: FLINK-21508
URL: https://issues.apache.org/jira/browse/FLINK-21508
Project: Flink
Issue Type: Bug
Components: API /
Iaroslav Zeigerman created FLINK-21507:
--
Summary: Given a sequence of multiple custom stream partitioning
operations only last transformation in sequence is applied while others are
dropped
Key: FLINK-21507
Qinghui Xu created FLINK-21506:
--
Summary: Option for setting mesos task user
Key: FLINK-21506
URL: https://issues.apache.org/jira/browse/FLINK-21506
Project: Flink
Issue Type: Improvement
If time allows then we could also include FLINK-21030 [1]. We are about to
merge this fix.
[1] https://issues.apache.org/jira/browse/FLINK-21030
Cheers,
Till
On Thu, Feb 25, 2021 at 4:13 PM Roman Khachatryan wrote:
> Hi everyone,
>
> The issue which caused the previous RC cancellation is now
Hi everyone,
The issue which caused the previous RC cancellation is now resolved [1].
There are two more issues that we'd like to include in 1.12.2 [2][3].
Yuan and I are going to prepare the next RC (#2) once they are resolved.
Please let us know if there are any other issues blocking the RC.
Aljoscha Krettek created FLINK-21505:
Summary: Enforce common savepoint format at the operator level
Key: FLINK-21505
URL: https://issues.apache.org/jira/browse/FLINK-21505
Project: Flink
Roman Khachatryan created FLINK-21504:
-
Summary: Enrich checkpoint barriers with information previous
checkpoint(s)
Key: FLINK-21504
URL: https://issues.apache.org/jira/browse/FLINK-21504
Dawid Wysakowicz created FLINK-21503:
Summary: Resource management time out on azure
Key: FLINK-21503
URL: https://issues.apache.org/jira/browse/FLINK-21503
Project: Flink
Issue Type:
Hi all,
Very thanks for the discussions!
A. Regarding how to avoid emitting records in notifyCheckpointComplete:
Currently the structure of a new sink is writer -> committer -> global
committer and the paralellism of global committer
must be one. By design it would be used in several cases:
Hi,
Sorry it took some time, here are my findings:
The sentiment was:
• This will only be an issue when you face it.
• Generally urging for semantics (batch > time of first query issued,
streaming > row level).
• Not necessarily introducing new functions, but rather
Hi, everyone.
I do some summaries about the discussion about the option. If the summary
has errors, please correct me.
`table.dml-sync`:
- take effect for `executeMultiSql` and sql client
- benefit: SQL script portability. One script for all platforms.
- drawback: Don't work for
Xintong Song created FLINK-21502:
Summary: Reduce frequency of global re-allocate resources
Key: FLINK-21502
URL: https://issues.apache.org/jira/browse/FLINK-21502
Project: Flink
Issue Type:
Hi everyone,
since Flink 1.9 we have supported two SQL planners. Most of the original
plan of FLIP-32 [1] has been implemented. The Blink code merge has been
completed and many additional features have been added exclusively to
the new planner. The new planner is now in a much better shape
Dawid Wysakowicz created FLINK-21501:
Summary: Sync Chinese documentation with FLINK-21343
Key: FLINK-21501
URL: https://issues.apache.org/jira/browse/FLINK-21501
Project: Flink
Issue
The `table.` prefix is meant to be a general option in the table
ecosystem. Not necessarily attached to Table API or SQL Client. That's
why SQL Client is also located in the `flink-table` module.
My main concern is the SQL script portability. Declaring the sync/async
behavior will happen in
Dawid Wysakowicz created FLINK-21500:
Summary: Failed to upload logs in Azure
Key: FLINK-21500
URL: https://issues.apache.org/jira/browse/FLINK-21500
Project: Flink
Issue Type: Bug
20 matches
Mail list logo
