Yes, it makes sense to rewrite img tags and other resources using {% link
... %}, but, for example,
wrote:
> Yes, I think this rule also applies to resources, e.g. "{% link
> fig/stream_barriers.svg %}". Because it will help us to prevent dead links.
> Please correct me if I'm wrong @Seth.
>
> B
Andrey Zagrebin created FLINK-18454:
---
Summary: Add a code contribution section about how to look for
what to contribute
Key: FLINK-18454
URL: https://issues.apache.org/jira/browse/FLINK-18454
Projec
Niels Basjes created FLINK-18455:
Summary: Building with JDK 9+ leads to problems on JDK 8
Key: FLINK-18455
URL: https://issues.apache.org/jira/browse/FLINK-18455
Project: Flink
Issue Type: B
Hi everyone,
Please review and vote on the release candidate #4 for the version 1.11.0, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
Hi,
I have both JDK 8 and 14 on my system and yesterday I ran into this
exception (I put the info I have in this ticket
https://issues.apache.org/jira/browse/FLINK-18455 ) :
java.lang.NoSuchMethodError:
java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
>From digging around (
https://st
- source does not contain binaries
- started a local cluster, logs are fine, examples run
- web submission works _in general_
However, a number of batch examples fail when submitted through the
WebUI with the following error:
Caused by: org.apache.flink.api.common.InvalidProgramException:
Job
What is the Java version Apache Flink is supposed to work with?
8 and 11. Non-LTS Java11+ releases _should work_, but we don't put in
effort to make it as convenient as for LTS releases. As such you have to
manually enable the java11 profile when compiling Flink.
I set the target version to
Hey Gordon,
I have updated the FLIP [1] to include support for configurable registration
strategies:
- Added 2 additional configuration keys
- Added Registration/De-registration Configuration section
- Updated Stream Consumer Registration/Tear Down section
- Remove rejected alternative (since we
Hi Chesnay,
Ok, so if someone uses a non-LTS version of Java (like 14) then how about
simply "pinning" it to the Java 11 compatibility?
I'm assuming no one uses Java 9 and/or 10 anymore so I'm ignoring those.
Then building with Java 8 will result in Java 8 code.
Building with Java 11, 12, 13, 14,
Hi, David. I am sorry for late reply.
I will check pages which were translated by me according to your reply.
Thank you so much.
Best,
Roc.
| |
Roc Marshal
|
|
邮箱：flin...@126.com
|
签名由 网易邮箱大师 定制
On 06/30/2020 15:20, David Anderson wrote:
Yes, it makes sense to rewrite img tags and othe
This is difficult to do since you cannot have multiple jdk activations
for a single profile in maven, and duplicating the entire profile for
all jdk versions isn't an option.
We _maybe_ could invert the behavior such that the Java 11 behavior is
the default, with a JDK 8 profile, but there may
Dian Fu created FLINK-18456:
---
Summary: CompressionFactoryITCase.testWriteCompressedFile fails
with "expected:<1> but was:<2>"
Key: FLINK-18456
URL: https://issues.apache.org/jira/browse/FLINK-18456
Project:
Thanks for preparing another RC!
As mentioned in the previous RC thread, it would be super helpful if the
release notes that are part of the documentation can be included [1]. It's
a significant time-saver to have read those first.
I found one more non-backward compatible change that would be wor
13 matches
Mail list logo
