godfrey he created FLINK-20435:
--
Summary: Refactor ExecNode
Key: FLINK-20435
URL: https://issues.apache.org/jira/browse/FLINK-20435
Project: Flink
Issue Type: Improvement
Reporter: g
Hi Lu
Flink guarantees backwards compatibility but not forwards compatibility and you
can find the compatibility table here [1].
Flink-1.11 introduced unaligned checkpoint which upgrades the savepoint version
to 3, and that's why Flink-1.9 cannot consume savepoint generated by Flink-1.11.
[1]
Avi Levi created FLINK-20434:
Summary: Getting The desired archetype does not exist
Key: FLINK-20434
URL: https://issues.apache.org/jira/browse/FLINK-20434
Project: Flink
Issue Type: Bug
Hi everyone,
It seems that all blockers for 1.12.0 have been resolved, this is the first
voting release candidate.
Please review and vote on the release candidate #2 for the version 1.12.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific commen
Dian Fu created FLINK-20433:
---
Summary: UnalignedCheckpointTestBase.execute failed with
"TestTimedOutException: test timed out after 300 seconds"
Key: FLINK-20433
URL: https://issues.apache.org/jira/browse/FLINK-20433
Dian Fu created FLINK-20432:
---
Summary: SQLClientSchemaRegistryITCase hangs
Key: FLINK-20432
URL: https://issues.apache.org/jira/browse/FLINK-20432
Project: Flink
Issue Type: Bug
Component
Huang Xingbo created FLINK-20431:
Summary:
KafkaSourceReaderTest.testCommitOffsetsWithoutAliveFetchers:133->lambda$testCommitOffsetsWithoutAliveFetchers$3:134
expected:<10> but was:<1>
Key: FLINK-20431
URL: https
Hi, Flink dev
Is it supported that a flink job in version 1.9 could restore from a
checkpoint taken from the same job using 1.11? The context is we are
migrating to version 1.11 and we need a backup plan for emergency fallback.
We did a test and it throws error:
```
Caused by: org.apache.flink.run
Huang Xingbo created FLINK-20430:
Summary: Broken links in deployment/index.zh.md
Key: FLINK-20430
URL: https://issues.apache.org/jira/browse/FLINK-20430
Project: Flink
Issue Type: Bug
Dian Fu created FLINK-20429:
---
Summary: KafkaTableITCase.testKafkaTemporalJoinChangelog failed
with unexpected results
Key: FLINK-20429
URL: https://issues.apache.org/jira/browse/FLINK-20429
Project: Flink
Dian Fu created FLINK-20428:
---
Summary:
ZooKeeperLeaderElectionConnectionHandlingTest.testConnectionSuspendedHandlingDuringInitialization
failed with "No result is expected since there was no leader elected before
stopping the server, yet"
Hi Till,
immediate benefit would be mostly nested tests for a better test structure
and new parameterized tests for less clutter (often test functionality is
split into parameterized test and non-parameterized test because of JUnit4
limitation). Additionally, having Java8 lambdas to perform fine-g
Till Rohrmann created FLINK-20427:
-
Summary: Remove CheckpointConfig.setPreferCheckpointForRecovery
because it can lead to data loss
Key: FLINK-20427
URL: https://issues.apache.org/jira/browse/FLINK-20427
Dawid Wysakowicz created FLINK-20426:
Summary: Broken links to hadoop.md
Key: FLINK-20426
URL: https://issues.apache.org/jira/browse/FLINK-20426
Project: Flink
Issue Type: Bug
C
Hi all,
Just wanted to express my support for the idea. I did miss certain
features of JUnit 5 already, an important one being much better support
for parameterized tests.
Best,
Dawid
On 30/11/2020 13:50, Arvid Heise wrote:
> Hi Chesnay,
>
> The vintage runner supports the old annotations, so w
Robert Metzger created FLINK-20425:
--
Summary: Change exit code in FatalExitExceptionHandler to be
different from JvmShutdownSafeguard
Key: FLINK-20425
URL: https://issues.apache.org/jira/browse/FLINK-20425
Doing a few required changes swiftly and then porting the remaining tests
bit by bit sounds like an approachable plan. However, it will still cost us
some effort I guess. What exactly would be the benefit of this change other
than streamlining a few things? Are there things which we cannot do at th
Hi Chesnay,
The vintage runner supports the old annotations, so we don't have to change
them in the first step.
The only thing that we need to change are all rules that do not extend
ExternalResource (e.g., TestWatcher used in TestLogger). This change needs
to be done swiftly as this affects the
I presume we cannot do the migration module-wise due to shared test
utilities that rely on JUnit interfaces?
On 11/30/2020 1:30 PM, Chesnay Schepler wrote:
Is it feasible that 2 people can do the migration within a short
time-frame (say, a week)?
Must the migration of a test be done in one go,
Is it feasible that 2 people can do the migration within a short
time-frame (say, a week)?
Must the migration of a test be done in one go, or can we for example
first rename all the Before/After annotations and then to the rest?
Are there any issues with other test dependencies (i.e., hamcrest,
zlzhang0122 created FLINK-20424:
---
Summary: The percent of acknowledged checkpoint seems incorrect
Key: FLINK-20424
URL: https://issues.apache.org/jira/browse/FLINK-20424
Project: Flink
Issue Ty
Dawid Wysakowicz created FLINK-20423:
Summary: Remove usage of {{site.baseurl}} from markdown files
Key: FLINK-20423
URL: https://issues.apache.org/jira/browse/FLINK-20423
Project: Flink
Xiao Huang created FLINK-20422:
--
Summary: Remove {{ site.baseurl }} from .html files in flink
documentation
Key: FLINK-20422
URL: https://issues.apache.org/jira/browse/FLINK-20422
Project: Flink
Jark Wu created FLINK-20421:
---
Summary: Support canal-protobuf format
Key: FLINK-20421
URL: https://issues.apache.org/jira/browse/FLINK-20421
Project: Flink
Issue Type: Sub-task
Components
Yun Tang created FLINK-20420:
Summary: ES6 ElasticsearchSinkITCase failed due to no output for
900 seconds
Key: FLINK-20420
URL: https://issues.apache.org/jira/browse/FLINK-20420
Project: Flink
Rui Li created FLINK-20419:
--
Summary: Insert fails due to failure to generate execution plan
Key: FLINK-20419
URL: https://issues.apache.org/jira/browse/FLINK-20419
Project: Flink
Issue Type: Bug
Roman Khachatryan created FLINK-20418:
-
Summary: NPE in IteratorSourceReader
Key: FLINK-20418
URL: https://issues.apache.org/jira/browse/FLINK-20418
Project: Flink
Issue Type: Bug
Yang Wang created FLINK-20417:
-
Summary: Handle "Too old resource version" exception in Kubernetes
watch more gracefully
Key: FLINK-20417
URL: https://issues.apache.org/jira/browse/FLINK-20417
Project: Fl
Sebastian Liu created FLINK-20416:
-
Summary: Need a cached catalog for batch SQL job
Key: FLINK-20416
URL: https://issues.apache.org/jira/browse/FLINK-20416
Project: Flink
Issue Type: Improve
29 matches
Mail list logo
