Re: [VOTE] Release 1.5.0, release candidate #2

Still facing same issue with Apache flink 1.5.1 while building from source. MVN : 3.2.5 Command : mvn clean install -DskipTests -Dscala.version=2.11.7 -Pvendor-repos -Dhadoop.version=2.7.3.2.6.2.0-205 Error : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:

Re: [VOTE] Release 1.5.0, release candidate #2

Same error on 3.5.2 ... Let me check rc3 also. -- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/

Re: [VOTE] Release 1.5.0, release candidate #2

Hi, Regarding the Kinesis consumer, fwiw we backported most of the changes to 1.4.x in our fork and running our pipelines with those. Thanks, Thomas On Tue, May 15, 2018 at 5:50 AM, Till Rohrmann wrote: > Thanks for the feedback. I actually have to cancel this RC because of the > following is

Re: [VOTE] Release 1.5.0, release candidate #2

We've had the enforcer-plugin issue before and neither Timo nor me could reproduce it locally. See FLINK-9091 and FLINK-9145 . On 15.05.2018 14:50, Till Rohrmann wrote: Thanks for the feedbac

Re: [VOTE] Release 1.5.0, release candidate #2

Thanks for the feedback. I actually have to cancel this RC because of the following issues [1, 2, 3, 4]. The issues are already fixed and I will create a new RC asap. @Ted, thanks for reporting the problem with the BindException. We should look into why this happens but as Stephan said it should n

Re: [VOTE] Release 1.5.0, release candidate #2

Can you try out mvn 3.5.2 ? I don't get the error when running the command line you gave. BTW 2.7.3.2.6.2.0-205 was quite old release. Cheers On Mon, May 14, 2018 at 7:15 AM, shashank734 wrote: > While building from source failing with following error : > > Failed to execute goal > org.apache

Re: [VOTE] Release 1.5.0, release candidate #2

While building from source failing with following error : Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (dependency-convergence) on project flink-bucketing-sink-test MVN Version : 3.0.5 Command : mvn clean install -DskipTests -Dscala.version=2.11.7 -Pven

Re: [VOTE] Release 1.5.0, release candidate #2

@TedYu - looks like a port collision in the testing setup. Will look into that, but I would not consider that a release blocker. On Fri, May 11, 2018 at 5:16 AM, Tzu-Li (Gordon) Tai wrote: > Hi Bowen, > > Thanks for bringing this up! > > Yes, I think we should definitely always test the Kinesis

Re: [VOTE] Release 1.5.0, release candidate #2

Hi Bowen, Thanks for bringing this up! Yes, I think we should definitely always test the Kinesis connector for releases. FYI, I think you can also add modification suggestions to the test plan so that the release manager is aware of that. Some of the more major Kinesis connector changes that I

Re: [VOTE] Release 1.5.0, release candidate #2

Hi Till, I found that only file and kafka connectors are tested in the plan. @Gordon, shall we test the Kinesis connector? AFAIK, there're some major changes and AWS library upgrades in Flink 1.5. I would have tested it myself but I don't use Kinesis anymore. Thanks, Bowen On Thu, May 10, 2018

Re: [VOTE] Release 1.5.0, release candidate #2

I ran the test suite twice and both failed with: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.784 sec <<< FAILURE! - in org.apache.flink.runtime.jobmanager.scheduler.ScheduleOrUpdateConsumersTest org.apache.flink.runtime.jobmanager.scheduler.ScheduleOrUpdateConsumersTest Time

[VOTE] Release 1.5.0, release candidate #2

Hi everyone, it took some time to compile the next release candidate but here we are: Please review and vote on the release candidate #2 for the version 1.5.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area