Agreed, as I said above:
I have the fix ready but we can do that in Flink 1.2.2. Very quickly,
though.
Best,
Aljoscha
> On 24. Apr 2017, at 13:19, Ufuk Celebi wrote:
>
> I agree with Till and would NOT cancel this release. It has been
> delayed already quite a bit already and the fea
I agree with Till and would NOT cancel this release. It has been
delayed already quite a bit already and the feature freeze for 1.3.0
is coming up (i.e. most contributors will be busy and not spend a lot
of time for 1.2.1).
– Ufuk
On Mon, Apr 24, 2017 at 9:31 AM, Till Rohrmann wrote:
> If this
If this bug was already present in 1.2.0, then I guess not many users have
used this feature. Otherwise we would have seen complaints on the mailing
list.
>From the JIRA issue description, it looks as if we have to fix it for 1.3.0
anyway. What about fixing it this week and then backporting it to
It means that users cannot restore from 1.2.0 to 1.2.0, 1.2.0 to 1.2.1, or
1.2.1 to 1.2.1. However, this only happens when using the CheckpointedRestoring
interface, which you have to do when you want to migrate away form the
Checkpointed interface.
tl;dr It’s not a new bug but one that was pre
@all: I'm sorry for being a bad release manager this time. I'm not spending
much time online these days. I hope to increase my dev@ list activity a
little bit next week.
@Aljoscha:
Does this mean that users can not upgrade from 1.2.0 to 1.2.1 ?
Can we make the minor versions easily compatible?
If
There is this (somewhat pesky) issue:
- https://issues.apache.org/jira/browse/FLINK-6353: Restoring using
CheckpointedRestoring does not work from 1.2 to 1.2
I have the fix ready but we can do that in Flink 1.2.2. Very quickly, though.
> On 20. Apr 2017, at 17:20, Henry Saputra wrote:
>
> LIC
LICENSE file exists
NOTICE file looks good
Signature files look good
Hash files look good
No 3rd party exes in source artifact
Source compiled and pass tests
Local run work
Run simple job on YARN
+1
- Henry
On Wed, Apr 12, 2017 at 4:06 PM, Robert Metzger wrote:
> Dear Flink community,
>
> Plea
+1 (binding) for the release
- checked all checksums and signatures
- started standalone clusters and ran Gelly example
Greg
> On Apr 12, 2017, at 7:06 PM, Robert Metzger wrote:
>
> Dear Flink community,
>
> Please vote on releasing the following candidate as Apache Flink version 1.2
> .1.
>
I downloaded and expanded flink-1.2.1-src.tgz one more time.
The failed tests are not in source tar ball.
Looks like I expanded the tar ball into the same directory for previous RC
last week.
Cheers
On Thu, Apr 20, 2017 at 1:32 AM, Aljoscha Krettek
wrote:
> @Ted What is the hash of the commit
@Ted What is the hash of the commit where you saw the failing test? I think it
might have been some intermediate commit because these tests are not in the
code anymore on the release branch.
> On 19. Apr 2017, at 18:35, Henry Saputra wrote:
>
> This should be the one: https://github.com/aljosc
This should be the one: https://github.com/aljoscha/FliRTT
On Wed, Apr 19, 2017 at 7:48 AM, Ted Yu wrote:
> Till:
> A bit curious: where can I find the Flirrt tool ?
>
> Thanks
>
> On Wed, Apr 19, 2017 at 5:24 AM, Till Rohrmann
> wrote:
>
> > +1 (binding) for the release
> >
> > - checked check
Till:
A bit curious: where can I find the Flirrt tool ?
Thanks
On Wed, Apr 19, 2017 at 5:24 AM, Till Rohrmann wrote:
> +1 (binding) for the release
>
> - checked checksums and signature
> - no dependencies added or removed
> - build Flink with Hadoop 2.7.1 and Scala 2.11 from sources and ran al
+1 (binding) for the release
- checked checksums and signature
- no dependencies added or removed
- build Flink with Hadoop 2.7.1 and Scala 2.11 from sources and ran all
tests
- Ran Flirrt locally, on standalone cluster and Yarn with Hadoop 2.7.1 and
Scala 2.10
Cheers,
Till
On Thu, Apr 13, 2017
Hi,
Unfortunately I cannot test run the rc as I am on vacation. But we have
been running pretty much the same build (+1-2 commits) in production for
some time now.
+1 from me
Gyula
On Thu, Apr 13, 2017, 08:27 Andrew Psaltis wrote:
> +1 -- checked out all code, built with all tests, ran local
+1 -- checked out all code, built with all tests, ran local cluster,
deployed example streaming jobs
On Thu, Apr 13, 2017 at 2:26 AM, Andrew Psaltis
wrote:
> Ted -- I did not see those errors. My environment is:
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:4
Ted -- I did not see those errors. My environment is:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T11:41:47-05:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_
I ran test suite where the following failed:
Failed tests:
StreamExecutionEnvironmentTest.testDefaultParallelismIsDefault:143
expected:<-1> but was:<24>
StreamExecutionEnvironmentTest.testMaxParallelismMustBeBiggerEqualParallelism
Expected test to throw an instance of java.lang.IllegalArgumentE
17 matches
Mail list logo
