Hi folks,
To move on with the FLIP, I will cut out eventTimeFetchLag out of scope and
go ahead with the remainder.
I will open a VOTE later to today.
Best,
Arvid
On Wed, Jul 28, 2021 at 8:44 AM Arvid Heise wrote:
> Hi Becket,
>
> I have updated the PR according to your suggestion (note that
Dawid Wysakowicz created FLINK-23556:
Summary: SQLClientSchemaRegistryITCase fails with " Subject ...
not found"
Key: FLINK-23556
URL: https://issues.apache.org/jira/browse/FLINK-23556
Project: Fl
Dawid Wysakowicz created FLINK-23557:
Summary: 'Resuming Externalized Checkpoint (hashmap, sync, no
parallelism change) end-to-end test' fails on Azure
Key: FLINK-23557
URL: https://issues.apache.org/jira/brow
Dawid Wysakowicz created FLINK-23558:
Summary: E2e tests fail because of quiesced system timers service
Key: FLINK-23558
URL: https://issues.apache.org/jira/browse/FLINK-23558
Project: Flink
Thanks a lot for providing the new staging repository. I dropped the 1440
and 1441 staging repositories, to avoid that other RC reviewers
accidentally look into it, or that we accidentally release it.
+1 (binding)
Checks:
- I didn't find any additional issues in the release announcement
- the pgp
Piotr Nowojski created FLINK-23559:
--
Summary: Enable periodic materialisation in tests
Key: FLINK-23559
URL: https://issues.apache.org/jira/browse/FLINK-23559
Project: Flink
Issue Type: Sub-
Hi Arvid,
I think it is OK to leave eventTimeFetchLag out of the scope of this FLIP
given that it may involve additional API changes.
5. RecordMetadata is currently not simplifying any code. By the current
> design RecordMetadata is a read-only data structure that is constant for
> all records in
Piotr Nowojski created FLINK-23560:
--
Summary: Performance regression on 29.07.2021
Key: FLINK-23560
URL: https://issues.apache.org/jira/browse/FLINK-23560
Project: Flink
Issue Type: Bug
Hi all,
I have a couple of questions after studying the FLIP and the docs:
1. What happens when one of the readers has two splits assigned and one of
the splits actually receives data?
2. If I understand it correctly the Kinesis Source uses dynamic shard
discovery by default (so in case of idlen
Dear devs,
I'd like to open a vote on FLIP-179: Expose Standardized Operator Metrics
[1] which was discussed in this thread [2].
The vote will be open for at least 72 hours unless there is an objection
or not enough votes.
The proposal excludes the implementation for the currentFetchEventTimeLag
Hi everyone,
I started the voting thread [1]. Please cast your vote there or ask
additional questions here.
Best,
Arvid
[1]
https://lists.apache.org/thread.html/r70d321b6aa62ab4e31c8b73552b2de7846c4d31ed6f08d6541a9b36e%40%3Cdev.flink.apache.org%3E
On Fri, Jul 30, 2021 at 10:46 AM Becket Qin w
zlzhang0122 created FLINK-23561:
---
Summary: Detail the container completed message
Key: FLINK-23561
URL: https://issues.apache.org/jira/browse/FLINK-23561
Project: Flink
Issue Type: Improvement
Robert Metzger created FLINK-23562:
--
Summary: Update CI docker image to latest java version (1.8.0_292)
Key: FLINK-23562
URL: https://issues.apache.org/jira/browse/FLINK-23562
Project: Flink
Han Yin created FLINK-23563:
---
Summary: Sometimes ‘Stop’ cannot stop the job
Key: FLINK-23563
URL: https://issues.apache.org/jira/browse/FLINK-23563
Project: Flink
Issue Type: Bug
Componen
zlzhang0122 created FLINK-23564:
---
Summary: Make taskmanager.out and taskmanager.err rollable
Key: FLINK-23564
URL: https://issues.apache.org/jira/browse/FLINK-23564
Project: Flink
Issue Type: I
Hi all,
I'd like to start a vote on FLIP-177: Extend Sink API [1] which provides
small extensions to the Sink API introduced through FLIP-143.
The vote will be open for at least 72 hours unless there is an objection or
not enough votes.
Note that the FLIP was larger initially and I cut down all
a
Hi Guowei, hi all,
The main drawback of the AsyncIO approach is the decreased flexibility. In
particular, as you mentioned for the advanced backpressure use cases, you
would need to chain several AsyncIOs:
>>>But whether a sink is overloaded not only depends on the queue size. It
> also depends o
Hey Guowei,
there is one additional aspect I want to highlight that is relevant for the
types of destinations we had in mind when designing the AsyncSink.
I'll again use Kinesis as an example, but the same argument applies to other
destinations. We are using the PutRecords API to persist up to
Hi Martijn,
1. Good question. The watermarks and statuses of the splits are first
aggregated before emitted through the reader. The watermark strategy of the
user is actually applied on all SourceOutputs (=splits). Since one split is
active and one is idle, the watermark of the reader will not adv
JING ZHANG created FLINK-23565:
--
Summary: Window TVF Supports session window in runtime
Key: FLINK-23565
URL: https://issues.apache.org/jira/browse/FLINK-23565
Project: Flink
Issue Type: Sub-tas
MING created FLINK-23566:
Summary: Mysql 8.0 Public Key Retrieval is not allowed
Key: FLINK-23566
URL: https://issues.apache.org/jira/browse/FLINK-23566
Project: Flink
Issue Type: Bug
Affects Ve
+1 (non-binding)
- Checked checksums and signatures: OK
- Built from source: OK
- Checked the flink-web PR
- find one typo about the number of the fixes and improvements
- Submit some jobs from sql-client to local cluster, checked the web-ui,
cp, sp, log, etc: OK
Best,
Godfrey
Xingbo Huang
+1 (non-binding)
- Checked checksums and signatures: OK
- Built from source: OK
- Checked the flink-web PR
- find one typo about flink version
- Submit some jobs from sql-client to local cluster, checked the web-ui,
cp, sp, log, etc: OK
Best,
Godfrey
Robert Metzger 于2021年7月30日周五 下午4:33写道：
>
wuyang created FLINK-23567:
--
Summary: Hive 1.1.0 failed to write using flink sql 1.3.1 because
the JSON class was not found
Key: FLINK-23567
URL: https://issues.apache.org/jira/browse/FLINK-23567
Project: Fl
Hui Wang created FLINK-23568:
Summary: Plaintext Java Keystore Password Risks in the
flink-conf.yaml File
Key: FLINK-23568
URL: https://issues.apache.org/jira/browse/FLINK-23568
Project: Flink
I
+1 (non-binding)
On Fri, Jul 30, 2021 at 3:55 AM Arvid Heise wrote:
> Dear devs,
>
> I'd like to open a vote on FLIP-179: Expose Standardized Operator Metrics
> [1] which was discussed in this thread [2].
> The vote will be open for at least 72 hours unless there is an objection
> or not enough
26 matches
Mail list logo
