[jira] [Created] (FLINK-9333) QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options

[Yazdan Shirvany (JIRA)]

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: Flink
  Issue Type: Bug
  Components: Documentation
Affects Versions: 1.4.2, 1.4.1
Reporter: Yazdan Shirvany


- Spelling fix for QuickStart Project Template for Java 

- Adding more details regarding changing JVM options in IntelliJ IDEA



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9332) Fix Codegen error of CallGenerator

[Ruidong Li (JIRA)]

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
  Components: Table API  SQL
Reporter: Ruidong Li
Assignee: Ruidong Li


function call may return null, but nullTerm did not handle it correctly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Tzu-Li (Gordon) Tai]

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 know of, in 1.5.0:
[FLINK-8484] Fix Kinesis consumer re-reading closed shards on restart
[FLINK-8648] Customizable shard-to-subtask assignment

There are also some other more minor changes such as adding metrics and exposing
access to some internal methods / classes for more flexibility.

As you mentioned, also taking account that we had some AWS library upgrades,
we should definitely include Kinesis connector in the test plan.

Cheers,
Gordon
On 11 May 2018 at 1:08:34 AM, Bowen Li (bowenl...@gmail.com) wrote:

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 at 10:04 AM, Ted Yu  wrote: 

> 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 elapsed: 9.784 sec <<< ERROR! 
> java.net.BindException: Address already in use 
> at sun.nio.ch.Net.bind0(Native Method) 
> at sun.nio.ch.Net.bind(Net.java:433) 
> at sun.nio.ch.Net.bind(Net.java:425) 
> at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) 
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel.socket.nio. 
> NioServerSocketChannel.doBind(NioServerSocketChannel.java:125) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannel$ 
> AbstractUnsafe.bind(AbstractChannel.java:485) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel.DefaultChannelPipeline$ 
> HeadContext.bind(DefaultChannelPipeline.java:1081) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel. 
> AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext. 
> java:502) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel. 
> AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel. 
> DefaultChannelPipeline.bind(DefaultChannelPipeline.java:904) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannel.bind( 
> AbstractChannel.java:198) 
> at 
> org.apache.flink.shaded.netty4.io.netty.bootstrap.AbstractBootstrap$2.run( 
> AbstractBootstrap.java:348) 
> at 
> org.apache.flink.shaded.netty4.io.netty.util.concurrent. 
> SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357) 
> at 
> org.apache.flink.shaded.netty4.io.netty.channel.nio. 
> NioEventLoop.run(NioEventLoop.java:357) 
> at 
> org.apache.flink.shaded.netty4.io.netty.util.concurrent. 
> SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111) 
> at 
> org.apache.flink.shaded.netty4.io.netty.util.concurrent. 
> DefaultThreadFactory$DefaultRunnableDecorator.run( 
> DefaultThreadFactory.java:137) 
> at java.lang.Thread.run(Thread.java:748) 
> 
> The test passes when run alone. 
> 
> On Thu, May 10, 2018 at 9:37 AM, Till Rohrmann  
> wrote: 
> 
> > 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 is available for your review, which includes: 
> > * JIRA release notes [1], 
> > * the official Apache source release and binary convenience releases to 
> be 
> > deployed to dist.apache.org [2], which are signed with the key with 
> > fingerprint 1F302569A96CFFD5 [3], 
> > * all artifacts to be deployed to the Maven Central Repository [4], 
> > * source code tag "release-1.5.0-rc2" [5], 
> > 
> > Please use this document for coordinating testing efforts: [6] 
> > 
> > The vote will be open for at least 72 hours. It is adopted by majority 
> > approval, with at least 3 PMC affirmative votes. 
> > 
> > Thanks, 
> > Your friendly Release Manager 
> > 
> > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa? 
> > projectId=12315522=12341764 
> > [2] http://people.apache.org/~trohrmann/flink-1.5.0-rc2/ 
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS 
> > [4] https://repository.apache.org/content/repositories/ 
> orgapacheflink-1155 
> > [5] https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h= 
> > 

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

[Bowen Li]

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 at 10:04 AM, Ted Yu  wrote:

> 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 elapsed: 9.784 sec  <<< ERROR!
> java.net.BindException: Address already in use
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:433)
>   at sun.nio.ch.Net.bind(Net.java:425)
>   at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.socket.nio.
> NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannel$
> AbstractUnsafe.bind(AbstractChannel.java:485)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.DefaultChannelPipeline$
> HeadContext.bind(DefaultChannelPipeline.java:1081)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.
> AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.
> java:502)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.
> AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.
> DefaultChannelPipeline.bind(DefaultChannelPipeline.java:904)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannel.bind(
> AbstractChannel.java:198)
>   at
> org.apache.flink.shaded.netty4.io.netty.bootstrap.AbstractBootstrap$2.run(
> AbstractBootstrap.java:348)
>   at
> org.apache.flink.shaded.netty4.io.netty.util.concurrent.
> SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357)
>   at
> org.apache.flink.shaded.netty4.io.netty.channel.nio.
> NioEventLoop.run(NioEventLoop.java:357)
>   at
> org.apache.flink.shaded.netty4.io.netty.util.concurrent.
> SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
>   at
> org.apache.flink.shaded.netty4.io.netty.util.concurrent.
> DefaultThreadFactory$DefaultRunnableDecorator.run(
> DefaultThreadFactory.java:137)
>   at java.lang.Thread.run(Thread.java:748)
>
> The test passes when run alone.
>
> On Thu, May 10, 2018 at 9:37 AM, Till Rohrmann 
> wrote:
>
> > 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 is available for your review, which includes:
> > * JIRA release notes [1],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 1F302569A96CFFD5 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-1.5.0-rc2" [5],
> >
> > Please use this document for coordinating testing efforts: [6]
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Your friendly Release Manager
> >
> > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12315522=12341764
> > [2] http://people.apache.org/~trohrmann/flink-1.5.0-rc2/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4] https://repository.apache.org/content/repositories/
> orgapacheflink-1155
> > [5] https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=
> > 37af4d7e7072958a6d8bdfc49de2ed3a5f66c889
> > [6] https://docs.google.com/document/d/1rJe_
> 6yDPBurnhipmcSeCnpYFnr1SAuHyOQ
> > N2-08mJYc/edit?usp=sharing
> >
> > Pro-tip: you can create a settings.xml file with these contents:
> >
> > 
> > 
> >   flink-1.5.0
> > 
> > 
> >   
> > flink-1.5.0
> > 
> >   
> > flink-1.5.0
> > 
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1155/
> > 
> >   
> >   
> > archetype
> > 
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1155/
> > 
> >   
> > 
> >   
> > 
> > 
> >
> > And reference that in you maven commands via --settings
> > path/to/settings.xml. This is useful for creating a quickstart based on
> the
> > staged release and for building against the staged jars.
> >
>

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

[Ted Yu]

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 elapsed: 9.784 sec  <<< ERROR!
java.net.BindException: Address already in use
  at sun.nio.ch.Net.bind0(Native Method)
  at sun.nio.ch.Net.bind(Net.java:433)
  at sun.nio.ch.Net.bind(Net.java:425)
  at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
  at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
  at
org.apache.flink.shaded.netty4.io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
  at
org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)
  at
org.apache.flink.shaded.netty4.io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1081)
  at
org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:502)
  at
org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487)
  at
org.apache.flink.shaded.netty4.io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:904)
  at
org.apache.flink.shaded.netty4.io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198)
  at
org.apache.flink.shaded.netty4.io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)
  at
org.apache.flink.shaded.netty4.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357)
  at
org.apache.flink.shaded.netty4.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
  at
org.apache.flink.shaded.netty4.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
  at
org.apache.flink.shaded.netty4.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
  at java.lang.Thread.run(Thread.java:748)

The test passes when run alone.

On Thu, May 10, 2018 at 9:37 AM, Till Rohrmann  wrote:

> 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 is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint 1F302569A96CFFD5 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.5.0-rc2" [5],
>
> Please use this document for coordinating testing efforts: [6]
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Your friendly Release Manager
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12315522=12341764
> [2] http://people.apache.org/~trohrmann/flink-1.5.0-rc2/
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> [4] https://repository.apache.org/content/repositories/orgapacheflink-1155
> [5] https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=
> 37af4d7e7072958a6d8bdfc49de2ed3a5f66c889
> [6] https://docs.google.com/document/d/1rJe_6yDPBurnhipmcSeCnpYFnr1SAuHyOQ
> N2-08mJYc/edit?usp=sharing
>
> Pro-tip: you can create a settings.xml file with these contents:
>
> 
> 
>   flink-1.5.0
> 
> 
>   
> flink-1.5.0
> 
>   
> flink-1.5.0
> 
>
> https://repository.apache.org/content/repositories/orgapacheflink-1155/
> 
>   
>   
> archetype
> 
>
> https://repository.apache.org/content/repositories/orgapacheflink-1155/
> 
>   
> 
>   
> 
> 
>
> And reference that in you maven commands via --settings
> path/to/settings.xml. This is useful for creating a quickstart based on the
> staged release and for building against the staged jars.
>

[VOTE] Release 1.5.0, release candidate #2

[Till Rohrmann]

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 is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.5.0-rc2" [5],

Please use this document for coordinating testing efforts: [6]

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Thanks,
Your friendly Release Manager

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12315522=12341764
[2] http://people.apache.org/~trohrmann/flink-1.5.0-rc2/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1155
[5] https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=
37af4d7e7072958a6d8bdfc49de2ed3a5f66c889
[6] https://docs.google.com/document/d/1rJe_6yDPBurnhipmcSeCnpYFnr1SAuHyOQ
N2-08mJYc/edit?usp=sharing

Pro-tip: you can create a settings.xml file with these contents:



  flink-1.5.0


  
flink-1.5.0

  
flink-1.5.0


https://repository.apache.org/content/repositories/orgapacheflink-1155/

  
  
archetype


https://repository.apache.org/content/repositories/orgapacheflink-1155/

  

  



And reference that in you maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.

[jira] [Created] (FLINK-9331) MesosResourceManager sometimes does not request new Containers

[Till Rohrmann (JIRA)]

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
  Issue Type: Bug
  Components: Distributed Coordination
Affects Versions: 1.5.0, 1.6.0
Reporter: Till Rohrmann
Assignee: Till Rohrmann
 Fix For: 1.5.0


Similar to FLINK-9190 we also have to request new Mesos tasks if a task is 
reported to have failed. Otherwise we might run into the same problem that 
allocation requests are not fulfilled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [ANNOUNCE] Two new committers: Xingcan Cui and Nico Kruber

[Kostas Kloudas]

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, 2018, at 2:06 AM, Peter Huang  wrote:
>>> 
>>> Congratulations Nico and Xingcan!
>>> 
>>> On Wed, May 9, 2018 at 11:04 AM, Thomas Weise  wrote:
>>> 
 Congrats!
 
 
 On Wed, May 9, 2018 at 10:14 AM, Bowen Li  wrote:
 
> Congratulations!
> 
> On Tue, May 8, 2018 at 11:06 PM, Zhijiang(wangzhijiang999) <
> wangzhijiang...@aliyun.com> wrote:
> 
>> Congratulations, Xingcan and Nico !
>> Nico is a good PR reviewer and I gained a lot from him.
>> :)--
> 发件人：Fabian
>> Hueske 发送时间：2018年5月9日(星期三) 02:53收件人：dev <
>> dev@flink.apache.org>主 题：[ANNOUNCE] Two new committers: Xingcan Cui
 and
>> Nico Kruber
>> Hi everyone,
>> 
>> I'm happy to announce that two members of the Flink community accepted
> the
>> offer of the PMC to become committers.
>> 
>> * Xingcan Cui has been contributing to Flink for about a year, focusing
> on
>> Flink's relational APIs (SQL & Table API). In the past year, Xingcan
 has
>> started design discussions, helped reviewing several pull requests, and
>> replied to questions on the user mailing list.
>> 
>> * Nico Kruber is an active contributor since 1.5 years
>> and worked mostly on
>> internal features, such as the blob manager and a new network stack.
 Nico
>> answers many questions on the user mailing list, reports lots of bugs
 and
>> is a very active PR reviewer.
>> 
>> Please join me in congratulating Xingcan and Nico.
>> 
>> Cheers,
>> Fabian
>> 
>> 
> 
 
>> 

[jira] [Created] (FLINK-9330) Improve logging of SlotPool for debugging purposes

[Till Rohrmann (JIRA)]

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: Improvement
  Components: Distributed Coordination
Affects Versions: 1.5.0
Reporter: Till Rohrmann
Assignee: Stephan Ewen
 Fix For: 1.5.0


In order to better debug problems with the {{SlotPool}} we should add better 
debug messages to this component. That way future problems with the slot 
allocation protocol will be much easier to debug.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9329) hasRowtimeAttribute will throw NPE if user use setProctimeAttribute for table source

[yuemeng (JIRA)]

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
  Issue Type: Bug
  Components: Table API  SQL
Reporter: yuemeng
Assignee: yuemeng


{{{code}}}

{{KafkaTableSource source = Kafka010JsonTableSource.builder() // ...  
.withSchema(TableSchema.builder() .field("sensorId", Types.LONG()) 
.field("temp", Types.DOUBLE()) // field "ptime" is of type SQL_TIMESTAMP 
.field("ptime", Types.SQL_TIMESTAMP()).build()) // declare "ptime" as 
processing time attribute .withProctimeAttribute("ptime") .build();}}

tableEnv.registerTableSource("flights", kafkaTableSource);

{{{code}}}

{{ }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9328) RocksDBStateBackend might use PlaceholderStreamStateHandle to restor due to StateBackendTestBase class not register snapshots in some UTs

[Yun Tang (JIRA)]

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.apache.org/jira/browse/FLINK-9328
 Project: Flink
  Issue Type: Bug
  Components: State Backends, Checkpointing
Affects Versions: 1.4.2
Reporter: Yun Tang
 Fix For: 1.5.0


Currently, StateBackendTestBase class does not register snapshots to 
SharedStateRegistry in testValueState, testListState, testReducingState, 
testFoldingState and testMapState UTs, which may cause RocksDBStateBackend to 
restore from PlaceholderStreamStateHandle during the 2nd restore procedure if 
one specific sst file both existed in the 1st snapshot and the 2nd snapshot 
handle.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

KPL in current stable 1.4.2 and below, upcoming problem

[Dyana Rose]

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 connector in any previous version looks
like they'll have an issue.

I'm not sure how/if you want to communicate this. We build Flink ourselves,
so I plan on having a look at any changes done to the Kinesis Sink in
v1.5.0 and then bumpimg the KPL version in our fork and rebuilding.

Thanks,
Dyana

below is the email we received (note: we're in eu-west-1):


Hello,



Your action is required: please update clients running Kinesis Producer
Library 0.12.5 or older or you will experience a breaking change to your
application.



We've discovered you have one or more clients writing data to Amazon
Kinesis Data Streams running an outdated version of the Kinesis Producer
Library. On 6/12 these clients will be impacted if they are not updated to
Kinesis Producer Library version 0.12.6 or newer. On 06/12 Kinesis Data
Streams will install ATS certificates which will prevent these outdated
clients from writing to a Kinesis Data Stream. The result of this change
will break any producer using KPL 0.12.5 or older.


* How do I update clients and applications to use the latest version of the
Kinesis Producer Library?

You will need to ensure producers leveraging the Kinesis Producer Library
have upgraded to version 0.12.6 or newer. If you operate older versions
your application will break due untrusted SSL certification.

Via Maven install Kinesis Producer Library version 0.12.6 or higher [2]

After you've configured your clients to use the new version, you're done.

* What if I have questions or issues?

If you have questions or issues, please contact your AWS Technical Account
Manager or AWS support and file a support ticket [3].

[1] https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-upgrades.html

[2] http://search.maven.org/#artifactdetails|com.amazonaws|amazo
n-kinesis-produ...


[3] https://aws.amazon.com/support



-  Amazon Kinesis Data Streams Team
-

Re: [ANNOUNCE] Two new committers: Xingcan Cui and Nico Kruber

[Amit Jain]

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 11:04 AM, Thomas Weise  wrote:
>>
>>> Congrats!
>>>
>>>
>>> On Wed, May 9, 2018 at 10:14 AM, Bowen Li  wrote:
>>>
 Congratulations!

 On Tue, May 8, 2018 at 11:06 PM, Zhijiang(wangzhijiang999) <
 wangzhijiang...@aliyun.com> wrote:

> Congratulations, Xingcan and Nico !
> Nico is a good PR reviewer and I gained a lot from him.
> :)--
 发件人：Fabian
> Hueske 发送时间：2018年5月9日(星期三) 02:53收件人：dev <
> dev@flink.apache.org>主 题：[ANNOUNCE] Two new committers: Xingcan Cui
>>> and
> Nico Kruber
> Hi everyone,
>
> I'm happy to announce that two members of the Flink community accepted
 the
> offer of the PMC to become committers.
>
> * Xingcan Cui has been contributing to Flink for about a year, focusing
 on
> Flink's relational APIs (SQL & Table API). In the past year, Xingcan
>>> has
> started design discussions, helped reviewing several pull requests, and
> replied to questions on the user mailing list.
>
> * Nico Kruber is an active contributor since 1.5 years
> and worked mostly on
> internal features, such as the blob manager and a new network stack.
>>> Nico
> answers many questions on the user mailing list, reports lots of bugs
>>> and
> is a very active PR reviewer.
>
> Please join me in congratulating Xingcan and Nico.
>
> Cheers,
> Fabian
>
>

>>>
>