I agree with you, Fabian.
I will add a small hint in exception and cast bigDecimal manually in test cases
-Original Message-
From: Fabian Hueske [mailto:fhue...@gmail.com]
Sent: Friday, October 28, 2016 7:17 PM
To: dev@flink.apache.org
Subject: Re: trouble with type casting
Hi Anton
Hi Anton,
it seems that the Table API validation is more strict than Calcite's SQL
validator (maybe because it is not aware of the actual implementation).
In principle, it is correct to prevent the auto-casting from BigDecimal to
double.
I think it is fine to request an explicit cast from users (
I'm working on flink-4743 issue
I tried write tests as Fabian suggested me
https://github.com/apache/flink/pull/2686#discussion_r85218584
and figure out that there is no implicit conversion of bigDecimal to double in
table api.
"power" function accept only double as operands.
all is okay when r
