Jing Ge created FLINK-25506:
---
Summary: Generate HBase Connector Options doc from
HBaseConnectorOptions
Key: FLINK-25506
URL: https://issues.apache.org/jira/browse/FLINK-25506
Project: Flink
Issue
built against the lowest Flink
> version they support and rest assured users with newer versions of
> Flink don't run into trouble.
>
> Thanks,
> Thomas
>
> On Wed, Dec 29, 2021 at 8:04 AM Jing Ge wrote:
> >
> > Hi Piotrek,
> >
> > thanks for asking. To be hone
of those is easier to
> provide and explain to the users.
>
> Of course the big missing piece after FLIP-197 is that we haven't agreed on
> any type of binary compatibility.
>
> Best,
> Piotrek
>
> śr., 29 gru 2021 o 14:07 Jing Ge napisał(a):
>
> > Hi everyone,
&
Hi everyone,
with great interest I have read all discussions [1][2][3] w.r.t. the (API?)
compatibility issues. The feedback coming from the Flink user's point of
view is very valuable. Many thanks for it. In these discussions, there were
many explanations that talked about backward and forward
Jing Ge created FLINK-25416:
---
Summary: Build unified Parquet BulkFormat for both Table API and
DataStream API
Key: FLINK-25416
URL: https://issues.apache.org/jira/browse/FLINK-25416
Project: Flink
Thanks Hang and Qingsheng for your effort and starting this discussion. As
additional information, I've created an umbrella ticket(
https://issues.apache.org/jira/browse/FLINK-25325). It is recommended to
create all JUnit5 migration related tasks under it, So we could track the
whole migration
Jing Ge created FLINK-25325:
---
Summary: Migration Flink from Junit4 to Junit5
Key: FLINK-25325
URL: https://issues.apache.org/jira/browse/FLINK-25325
Project: Flink
Issue Type: New Feature
Jing Ge created FLINK-25324:
---
Summary: Migration Flink from Junit4 to Junit5
Key: FLINK-25324
URL: https://issues.apache.org/jira/browse/FLINK-25324
Project: Flink
Issue Type: New Feature
Hi all,
I took a close look at assertj and found there are two concepts for writing
tests with two entry points interfaces: WithAssertions for normal style and
BDDAssertions for BDD style. I would not suggest using them in one project
simultaneously. Since all related work done previously were
+1 LGTM. Many thanks for your effort!
On Mon, Dec 13, 2021 at 8:28 PM Chesnay Schepler wrote:
> Hi everyone,
>
> This vote is for the emergency patch releases for 1.11, 1.12, 1.13 and
> 1.14 to address CVE-2021-44228.
> It covers all 4 releases as they contain the same changes (upgrading
>
+1
As I suggested to publish the blog post last week asap, users have been
keen to have such urgent releases. Many thanks for it.
On Mon, Dec 13, 2021 at 8:29 AM Konstantin Knauf wrote:
> +1
>
> I didn't think this was necessary when I published the blog post on Friday,
> but this has made
Jing Ge created FLINK-25220:
---
Summary: Writing an architectural rule for all IT cases w.r.t.
MiniCluster
Key: FLINK-25220
URL: https://issues.apache.org/jira/browse/FLINK-25220
Project: Flink
Thanks Chesnay for bringing this up for discussion. +1 for Java 8
deprecation. Every decision has pros and cons. All concerns mentioned
previously are fair enough. I think that the active support for Java 8
ending in 4 months will have an impact on the projects that still stick
with Java 8 and on
Jing Ge created FLINK-24741:
---
Summary: Deprecate FileRecordFormat, use StreamFormat instead
Key: FLINK-24741
URL: https://issues.apache.org/jira/browse/FLINK-24741
Project: Flink
Issue Type
Jing Ge created FLINK-24721:
---
Summary: Update the based on the Maven official
indication
Key: FLINK-24721
URL: https://issues.apache.org/jira/browse/FLINK-24721
Project: Flink
Issue Type
Since images do not work with pony mail, enclosed please find them as
attachments.
Best regards
Jing
On Thu, Oct 14, 2021 at 6:43 PM Jing Ge wrote:
> Agree. If the description contains more information than the return tag
> comment. Part of content overlap is acceptable. Otherwise I
transitionState(ExecutionState currentState,
> ExecutionState newState);
>
> but that's not always the case.
>
> At the same time I don't have hard feelings either direction. After all it
> doesn't seem to be that big of an issue even if we leave it as is.
>
> Best,
> Piotrek
>
Hi Flink developers,
It might be a good idea to avoid the redundant javadoc comment found in
some classes, e.g. org.apache.flink.core.fs.Path w.r.t. the @Return tag
comment on some methods.
To make the discussion clear, let's focus on a concrete example(there are
many more):
> /**
> * Returns
701 - 718 of 718 matches
Mail list logo
