Thank for your explanation.
Yes the InetSocketAddress you used is imported from java.net instead of
elaticsearh2. Very cool!
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/InetSocketAddress-is-not-serializable-when-building-ElasticSearch2
why List can become serilizable?
>
> Best,
>
> Sendoh
>
>
>
> --
> View this message in context:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/InetSocketAddress-is-not-serializable-when-building-ElasticSearch2-connector-tp5296p5299.html
> Sen
Can I ask why List can become serilizable?
Best,
Sendoh
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/InetSocketAddress-is-not-serializable-when-building-ElasticSearch2-connector-tp5296p5299.html
Sent from the Apache Flink User Mailing
Thank you. Very nice usage and It works!
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/InetSocketAddress-is-not-serializable-when-building-ElasticSearch2-connector-tp5296p5298.html
Sent from the Apache Flink User Mailing List archive
>
>
> --
> View this message in context:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/InetSocketAddress-is-not-serializable-tp5296.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive
> at Nabble.com.
>
ntext:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/InetSocketAddress-is-not-serializable-tp5296.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
