After upgrade i started getting this exception, is this a bug?
2017-06-05 23:45:03,423 INFO
org.apache.flink.runtime.executiongraph.ExecutionGraph- UTCStream ->
Sink: UTC sink (2/12) (f78ef7f7368d27f414ebb9d0db7a26c8) switched from
RUNNING to FAILED.
java.lang.Exception: Could not perfor
Hi,
Thanks for reporting this.
This is a know issue to be fixed in the upcoming 1.3.1:
https://issues.apache.org/jira/browse/FLINK-6844.
Regards,
Gordon
On 6 June 2017 at 1:47:53 AM, rhashmi (rizhas...@hotmail.com) wrote:
After upgrade i started getting this exception, is this a bug?
2017
Thanks for sharing ticket reference. Is there any time line as this is
blocker?
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Exception-in-Flink-1-3-0-tp13493p13500.html
Sent from the Apache Flink User Mailing List archive. mailing list ar
AFAIK, the release process for 1.3.1 should hopefully start within the next
days.
There’s already a few critical fixes on the waiting list.
On 6 June 2017 at 9:34:40 AM, rhashmi (rizhas...@hotmail.com) wrote:
Thanks for sharing ticket reference. Is there any time line as this is
blocker?
Any update when 1.3.1 will be available?
Our current copy is 1.2.0 but that has separate issue(invalid type code:
00).
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/invalid-type-code-00-td13326.html#a13332
--
View this message in context:
http://apache-flink-user-mailin
