Ted, The artifacts are already in maven central.
https://search.maven.org/#search|ga|1|g%3A%22org.apache.flink%22
Notice that google somehow puts always that mvnrepository.com website
mirror first in the results, even if it is almost always outdated. I
had the same problem when checking for jars b
Francisco Rosa created FLINK-6808:
-
Summary: Stream join fails when checkpointing is enabled
Key: FLINK-6808
URL: https://issues.apache.org/jira/browse/FLINK-6808
Project: Flink
Issue Type: B
Robert:
Do you know when maven artifacts would be populated ?
Currently I don't see 1.3.0 here:
https://mvnrepository.com/artifact/org.apache.flink/flink-core
Thanks
On Thu, Jun 1, 2017 at 7:48 AM, Robert Metzger wrote:
> The Apache Flink community is pleased to announce the release of Apache
Francisco Rosa created FLINK-6807:
-
Summary: Elasticsearch 5 connector artifact not published to maven
Key: FLINK-6807
URL: https://issues.apache.org/jira/browse/FLINK-6807
Project: Flink
Is
Bowen Li created FLINK-6806:
---
Summary: rocksdb is not listed as state backend in doc
Key: FLINK-6806
URL: https://issues.apache.org/jira/browse/FLINK-6806
Project: Flink
Issue Type: Bug
C
Shannon Carey created FLINK-6805:
Summary: Flink Cassandra connector dependency on Netty disagrees
with Flink
Key: FLINK-6805
URL: https://issues.apache.org/jira/browse/FLINK-6805
Project: Flink
And here's the PR for the new Docker images:
https://github.com/docker-library/official-images/pull/3006
(It was merged 10 min ago; the new images should become available by
tomorrow)
--
Patrick Lucas
On Thu, Jun 1, 2017 at 7:36 PM, Eron Wright wrote:
> Opened a PR for Homebrew update to `apac
Hi All,
I updated my pom file to use the newly release 1.3.0, and my build failed.
Looks like there is no flink connector for ES5 with version 1.3.0.
Could you someone release it ?
Am I using the right artifactId connector for ES5/1.3.0 ?
Thanks,
Fritz
org.
Opened a PR for Homebrew update to `apache-flink` formula:
https://github.com/Homebrew/homebrew-core/pull/14151
On Thu, Jun 1, 2017 at 7:48 AM, Robert Metzger wrote:
> The Apache Flink community is pleased to announce the release of Apache
> Flink 1.3.0.
>
> Apache Flink® is an open-source strea
I tried the second approach before and it results in the error with
scala.binary.version I attached, which is the same Ted got. I use it though
for other modules and it works.
I will try the first approach soon.
Z pozdrowieniami! / Cheers!
Dawid Wysakowicz
*Data/Software Engineer*
Skype: dawid
That removes the error.
However, looks like tests from other module(s) are run as well.
Just an example:
16:12:53,103 INFO
org.apache.flink.runtime.taskmanager.TaskManagerRegistrationTest -
=
Ah, I forgot that you also have to add “-Pjdk8” to activate the Java 8 profile.
Otherwise the flink-java8 module will not be referenced in the main pom.
> On 1. Jun 2017, at 17:42, Ted Yu wrote:
>
> When using the second approach (install followed by 'mvn verify'), I got
> the following:
>
> [
I’d like to propose keeping the same schedule but move branch forking from the
feature freeze to the code freeze. The early fork required duplicate
verification and commits for numerous bug fixes and minor features which had
been reviewed but were still queued. There did not look to be much new
When using the second approach (install followed by 'mvn verify'), I got
the following:
[ERROR] Failed to execute goal on project flink-java8_2.10: Could not
resolve dependencies for project
org.apache.flink:flink-java8_2.10:jar:1.4-SNAPSHOT: Failed to collect
dependencies at
org.apache.flink:flin
Hi all,
Flink 1.2 was released on February 2, Flink 1.3 on June 1, which means
we've managed to release Flink 1.3 in almost exactly 4 months!
For the 1.4 release, I've put the following deadlines into the wiki [1]:
*Next scheduled major release*: 1.4.0
*Feature freeze (branch forking)*: 4. Sept
When I used the command given by Aljoscha, I got:
https://pastebin.com/8WTGvdFQ
FYI
On Thu, Jun 1, 2017 at 8:17 AM, Aljoscha Krettek
wrote:
> Hi,
>
> I think you can use something like
>
> mvn verify -am -pl flink-java8
>
> (From the base directory)
>
> The -pl flag will tell maven to only do
Hi,
I think you can use something like
mvn verify -am -pl flink-java8
(From the base directory)
The -pl flag will tell maven to only do that module while -am tells it to also
builds its dependencies. This might or might not also run the tests on the
dependent-upon projects, I’m not sure.
As
Till Rohrmann created FLINK-6804:
Summary: Inconsistent state migration behaviour between different
state backends
Key: FLINK-6804
URL: https://issues.apache.org/jira/browse/FLINK-6804
Project: Flink
The Apache Flink community is pleased to announce the release of Apache
Flink 1.3.0.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
applications.
The release is available for download at:
https://fl
Till Rohrmann created FLINK-6803:
Summary: Add test for PojoSerializer when Pojo changes
Key: FLINK-6803
URL: https://issues.apache.org/jira/browse/FLINK-6803
Project: Flink
Issue Type: Impro
Till Rohrmann created FLINK-6802:
Summary: PojoSerializer does not create ConvertDeserializer for
removed/added fields
Key: FLINK-6802
URL: https://issues.apache.org/jira/browse/FLINK-6802
Project: Fl
Hi devs!
Recently I tried running* mvn verify* just for the *flink-java8* module (to
run those tests locally) and it fails with the following error:
[ERROR] Failed to execute goal on project flink-java8_2.10: Could not
> resolve dependencies for project
> org.apache.flink:flink-java8_2.10:jar:1.4
Till Rohrmann created FLINK-6801:
Summary: PojoSerializerConfigSnapshot cannot deal with missing
Pojo fields
Key: FLINK-6801
URL: https://issues.apache.org/jira/browse/FLINK-6801
Project: Flink
Till Rohrmann created FLINK-6800:
Summary: PojoSerializer ignores added pojo fields
Key: FLINK-6800
URL: https://issues.apache.org/jira/browse/FLINK-6800
Project: Flink
Issue Type: Bug
Till Rohrmann created FLINK-6799:
Summary: PojoSerializer does not check field types when being
deserialized
Key: FLINK-6799
URL: https://issues.apache.org/jira/browse/FLINK-6799
Project: Flink
Robert Metzger created FLINK-6798:
-
Summary: Remove/update documentation about network buffer tuning
Key: FLINK-6798
URL: https://issues.apache.org/jira/browse/FLINK-6798
Project: Flink
Issue
David Anderson created FLINK-6797:
-
Summary: building docs fails with bundler 1.15
Key: FLINK-6797
URL: https://issues.apache.org/jira/browse/FLINK-6797
Project: Flink
Issue Type: Bug
I've given you contributor permissions.
On 01.06.2017 15:10, Robert Metzger wrote:
Hi,
you don't need to file an ICLA. Can you please subscribe to the
dev@flink.apache.org mailing list by sending an empty email to
dev-subscr...@flink.apache.org?
So far, your messages were manually accepted.
On
Hi,
you don't need to file an ICLA. Can you please subscribe to the
dev@flink.apache.org mailing list by sending an empty email to
dev-subscr...@flink.apache.org?
So far, your messages were manually accepted.
On Thu, Jun 1, 2017 at 2:27 PM, jinchul wrote:
> Hello,
>
> Thanks for your kind answe
Hello,
Thanks for your kind answer. My JIRA's username is "jinchul". By the way,
should I fill out and send a ICLA document before contributing?
Best regards,
Jinchul
--
View this message in context:
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Willing-to-contribute-to-Flink
Till Rohrmann created FLINK-6796:
Summary: Allow setting the user code class loader for
AbstractStreamOperatorTestHarness
Key: FLINK-6796
URL: https://issues.apache.org/jira/browse/FLINK-6796
Project:
Hi Timo,
I agree that not having the documentation available for the new features is
not good.
I'll do a pass over all the open documentation PRs and try to merge as many
as possible. If I have the feeling, that we have enough docs, I'll release
1.3.0.
For the table API, I can put a note into the
Chesnay Schepler created FLINK-6795:
---
Summary: Activate checkstyle for runtime/process
Key: FLINK-6795
URL: https://issues.apache.org/jira/browse/FLINK-6795
Project: Flink
Issue Type: Impro
Chesnay Schepler created FLINK-6794:
---
Summary: Activate checkstyle for migration/*
Key: FLINK-6794
URL: https://issues.apache.org/jira/browse/FLINK-6794
Project: Flink
Issue Type: Improvem
Chesnay Schepler created FLINK-6793:
---
Summary: Activate checkstyle for runtime/metrics
Key: FLINK-6793
URL: https://issues.apache.org/jira/browse/FLINK-6793
Project: Flink
Issue Type: Impro
Chesnay Schepler created FLINK-6792:
---
Summary: flink-yarn-tests always fail on travis
Key: FLINK-6792
URL: https://issues.apache.org/jira/browse/FLINK-6792
Project: Flink
Issue Type: Bug
Nico Kruber created FLINK-6791:
--
Summary: Using MemoryStateBackend as checkpoint stream back-end
may block checkpoint/savepoint creation
Key: FLINK-6791
URL: https://issues.apache.org/jira/browse/FLINK-6791
Hello,
it's great that you want to contribute!
If you give me your JIRA user name i can give you contributor
permissions, so you can assign issues to yourself.
Note that parts of JIRA are not /completely/ up to date (especially in
the older parts); when you're unsure whether
the JIRA is still
38 matches
Mail list logo
