You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@flink.apache.org by Flink CI <fl...@foxmail.com> on 2019/12/26 04:52:52 UTC

Broken: apache/flink#41778 (master - fb0cd0e)

|  [

apache

/

flink

](https://travis-ci.org/apache/flink)  
---  
  
![branch icon](https://s3.amazonaws.com/travis-email-
assets/branch.png)[master](https://github.com/apache/flink/tree/master)  
  
|

![build hasfailed](https://s3.amazonaws.com/travis-email-assets/status-
failed.png)

[Build #41778 broken](https://travis-ci.org/apache/flink/builds/629545190)

![arrow to build time](https://s3.amazonaws.com/travis-email-assets/failure-
arrow.png)

![clock icon](https://s3.amazonaws.com/travis-email-assets/time.png)20 mins,
39 secs  
  
---  
  
![Jark Wu
avatar](https://secure.gravatar.com/avatar/0ca02b51276c3dc1852bc396ad1ade4b.jpg)Jark
Wu

[fb0cd0e CHANGESET
->](https://github.com/apache/flink/compare/0ba4a2b4cc2b...fb0cd0ee3cc0)  
  
[FLINK-15313][table-blink] Fix can't insert decimal data into sink using
TypeInformation  
  
The root problem is we use TypeInformation for sink code generation which  
loses the precision of decimal type. This result in the illegal accessing to  
the internal Decimal value. The fixing including:  
  
1\. Add validation for query and sink field types should be compatible
(including precision)  
2\. If not compatible, an implicit cast is added (this makes sure that it is
still correct  
to access internal decimal data using sink field type, e.g. genToExternal)  
3\. Checks logical schema (from DDL) and physical schema (from
TableSink#getConsumedDataType)  
are compatible.  
4\. Use new type system for sink code generation  
  
This closes #10667