Hi,

I've tried Flink with ES6, and its causing exception thrown in ES6. Is the fix 
just matter of bumping es client version to 5.6 ?
Could anyone familiar with ES connector confirm ? If this is just a matter of 
bumping the es client version, can we have this simple change in Flink 1.4 ?

Thanks,
Fritz


[2017-11-17T17:06:31,833][WARN ][o.e.t.n.Netty4Transport  ] [a6z4L9y] exception 
caught on transport layer [[id: 0xc77396b0, L:/10.32.0.85:9300 - 
R:/10.32.0.82:34814]], closing connection                                       
                                             java.lang.IllegalStateException: 
Received message from unsupported version: [5.0.0] minimal compatible version 
is: [5.6.0]
        at 
org.elasticsearch.transport.TcpTransport.ensureVersionCompatibility(TcpTransport.java:1415)
 ~[elasticsearch-6.0.0.jar:6.0.0]
        at 
org.elasticsearch.transport.TcpTransport.messageReceived(TcpTransport.java:1362)
 ~[elasticsearch-6.0.0.jar:6.0.0]
        at 
org.elasticsearch.transport.netty4.Netty4MessageChannelHandler.channelRead(Netty4MessageChannelHandler.java:60)
 ~[transport-netty4-6.0.0.jar:6.0.0]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
 [netty-codec-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:297)
 [netty-codec-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:413)
 [netty-codec-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
 [netty-codec-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:241) 
[netty-handler-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]                                
                                                                                
          at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]                                
                                                                                
   at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]                                
                                                                                
   at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]                                
                                                                                
                   at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:134)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:644) 
[netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:544)
 [netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:498) 
[netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:458) 
[netty-transport-4.1.13.Final.jar:4.1.13.Final]
        at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
 [netty-common-4.1.13.Final.jar:4.1.13.Final]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]

> On Nov 15, 2017, at 12:07 PM, Fritz Budiyanto <fbudi...@icloud.com> wrote:
> 
> Hi All,
> 
> ES6 is GA today, and I wonder if Flink-ES5 connector fully support ES6 ? Any 
> caveat we need to know ?
> 
> Thanks,
> Fritz

Reply via email to