Congrats!
On Thu, May 10, 2018 at 10:10 AM, Xingcan Cui wrote:
> Thanks, everyone!
>
> It’s an honor which inspires me to devote more to our community.
>
> Regards,
> Xingcan
>
>> On May 10, 2018, at 2:06 AM, Peter Huang wrote:
>>
>> Congratulations Nico and Xingcan!
>>
>> On Wed, May 9, 2018 at
Hello,
We've received notification from AWS that the Kinesis Producer Library
versions < 0.12.6 will stop working after the 12th of June (assuming the
date in the email is in US format...)
Flink v1.5.0 has the KPL version at 0.12.6 so it will be fine when it's
released. However using the kinesis
Yun Tang created FLINK-9328:
---
Summary: RocksDBStateBackend might use
PlaceholderStreamStateHandle to restor due to StateBackendTestBase class not
register snapshots in some UTs
Key: FLINK-9328
URL: https://issues.apach
yuemeng created FLINK-9329:
--
Summary: hasRowtimeAttribute will throw NPE if user use
setProctimeAttribute for table source
Key: FLINK-9329
URL: https://issues.apache.org/jira/browse/FLINK-9329
Project: Flink
Till Rohrmann created FLINK-9330:
Summary: Improve logging of SlotPool for debugging purposes
Key: FLINK-9330
URL: https://issues.apache.org/jira/browse/FLINK-9330
Project: Flink
Issue Type:
Congratulations to both of you guys!
> On May 10, 2018, at 9:41 AM, Amit Jain wrote:
>
> Congrats!
>
> On Thu, May 10, 2018 at 10:10 AM, Xingcan Cui wrote:
>> Thanks, everyone!
>>
>> It’s an honor which inspires me to devote more to our community.
>>
>> Regards,
>> Xingcan
>>
>>> On May 10,
Till Rohrmann created FLINK-9331:
Summary: MesosResourceManager sometimes does not request new
Containers
Key: FLINK-9331
URL: https://issues.apache.org/jira/browse/FLINK-9331
Project: Flink
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
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
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
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
Ruidong Li created FLINK-9332:
-
Summary: Fix Codegen error of CallGenerator
Key: FLINK-9332
URL: https://issues.apache.org/jira/browse/FLINK-9332
Project: Flink
Issue Type: Bug
Compon
Yazdan Shirvany created FLINK-9333:
--
Summary: QuickStart Docs Spelling fix and some info regarding
IntelliJ JVM Options
Key: FLINK-9333
URL: https://issues.apache.org/jira/browse/FLINK-9333
Project:
13 matches
Mail list logo