Hi Till,
Sorry for the late reply. The previous period, I focused on another urgent
work,
and suspended the releasing work. I've recently restarted it.
Best,
Godfrey
Till Rohrmann 于2021年7月13日周二 下午8:36写道：
> Hi Godfrey,
>
> Are you continuing with the 1.11.4 release process?
>
> Cheers,
> Till
Shengkai Fang created FLINK-23446:
-
Summary: Refactor SQL Client end to end tests
Key: FLINK-23446
URL: https://issues.apache.org/jira/browse/FLINK-23446
Project: Flink
Issue Type:
Dian Fu created FLINK-23445:
---
Summary: Separate data and timer connection into different
channels for Python Table API operators
Key: FLINK-23445
URL: https://issues.apache.org/jira/browse/FLINK-23445
Hui Wang created FLINK-23444:
Summary: Slf4j 1.7.15 has the high-risk vulnerability CVE-2018-8088
Key: FLINK-23444
URL: https://issues.apache.org/jira/browse/FLINK-23444
Project: Flink
Issue
Xintong Song created FLINK-23443:
Summary: LaunchCoordinatorTest fails on azure
Key: FLINK-23443
URL: https://issues.apache.org/jira/browse/FLINK-23443
Project: Flink
Issue Type: Bug
Thanks @Till Rohrmann for starting this discussion
Firstly, I try to understand the benefit of shorter heartbeat timeout.
IIUC, it will make the JobManager aware of
TaskManager faster. However, it seems that only the standalone cluster
could benefit from this. For Yarn and
native Kubernetes
Yubin Li created FLINK-23442:
Summary: FileSystemFactory refactor in flink-table-runtime
Key: FLINK-23442
URL: https://issues.apache.org/jira/browse/FLINK-23442
Project: Flink
Issue Type:
Yuan Mei created FLINK-23441:
Summary: Remove CheckpointOptions Argument away from
Snapshotable#snapshot
Key: FLINK-23441
URL: https://issues.apache.org/jira/browse/FLINK-23441
Project: Flink
yang89520 created FLINK-23440:
-
Summary: The "State. Backend" of "Flink-CONF.YAML" is inconsistent
with the documentation
Key: FLINK-23440
URL: https://issues.apache.org/jira/browse/FLINK-23440
Project:
This proposal to narrow the definition of idleness to focus on the
event-time clock is great.
Please mention that the "temporary status toggle" code will be removed.
I agree with adding the markActive() functionality, for symmetry. Speaking
of symmetry, could we now include the minor
Seth Wiesman created FLINK-23439:
Summary: Update "Local Installation" Page
Key: FLINK-23439
URL: https://issues.apache.org/jira/browse/FLINK-23439
Project: Flink
Issue Type: Improvement
Hi Guowei,
1. your idea is quite similar to FLIP-171 [1]. The question is if we
implement FLIP-171 based on public interfaces (which would require exposing
MailboxExecutor as described here in FLIP-177) or if it's better to
implement it internally and hide it.
The first option is an abstract base
Martijn Visser created FLINK-23438:
--
Summary: Bump httpclient from 4.5.3 to 4.5.13
Key: FLINK-23438
URL: https://issues.apache.org/jira/browse/FLINK-23438
Project: Flink
Issue Type:
+1 (binding)
* checked the website PR
* verified changed versions and NOTICE files since version 13.0
* verified the checksum and the signature
Best,
Dawid
On 19/07/2021 10:58, Timo Walther wrote:
> +1 (binding)
>
> I went through all commits one more time and could not spot anything
>
+1 to this change!
When I was working on the reactive mode blog post [1] I also ran into this
issue, leading to a poor "out of the box" experience when scaling down.
For my experiments, I've chosen a timeout of 8 seconds, and the cluster has
been running for 76 days (so far) on Kubernetes.
I also
Hi Becket,
Thank you for the detailed reply!
My understanding of your comments is that most of option-1 looks good
except its change of the Transformer semantics. Please see my reply inline.
On Tue, Jul 20, 2021 at 11:43 AM Becket Qin wrote:
> Hi Dong, Zhipeng and Fan,
>
> Thanks for the
Maciej Bryński created FLINK-23437:
--
Summary: Connection leak in XaFacadePoolingImpl
Key: FLINK-23437
URL: https://issues.apache.org/jira/browse/FLINK-23437
Project: Flink
Issue Type: Bug
Hi Becket,
Thanks for the review! I totally agree that it would be easier for people
to discuss if we can list the fundamental difference between these two
proposals. (So I want to make the discussion even shorter)
In my opinion, the fundamental difference between proposal-1 and proposal-2
is
Hi, Avrid
Thank you Avrid for perfecting Sink through this FLIP. I have two little
questions
1. What do you think of us directly providing an interface as follows? In
this way, there may be no need to expose the Mailbox to the user. We can
implement an `AsyncSinkWriterOperator` to control the
吴彦祖 created FLINK-23436:
---
Summary: When implements the LookupFunction In SQL that indirect
extends (Async)TableFunction, throw exception
Key: FLINK-23436
URL: https://issues.apache.org/jira/browse/FLINK-23436
Would it be easier to understand if the method would accept a Supplier
instead?
On 20/07/2021 05:36, Becket Qin wrote:
In that case, do we still need the metric here? It seems we are creating a
"global variable" which users may potentially use. I am wondering how much
additional convenience it
godfrey he created FLINK-23435:
--
Summary: Improve the exception message when a query has lateral
table join without 'AS' which return type is simple type
Key: FLINK-23435
URL:
22 matches
Mail list logo
