Hi,
big +1 for this!
Thank you Jark for writing the great document. I totally agree with the
proposal. It not only keep the English document same as before but also
proposes a way to integrate with Chinese ones.
Best, Hequn
On Mon, Feb 4, 2019 at 6:18 PM Fabian Hueske wrote:
> Happy Chinese
Alexey Trenikhin created FLINK-11523:
Summary: TestHarness should provide way to configure
TypeSerailizers for side output
Key: FLINK-11523
URL: https://issues.apache.org/jira/browse/FLINK-11523
Dian Fu created FLINK-11522:
---
Summary: Deprecate ExternalCatalogTable.builder()
Key: FLINK-11522
URL: https://issues.apache.org/jira/browse/FLINK-11522
Project: Flink
Issue Type: Task
RTRIM is not the only solution. It is also possible to cast all literals
of a CASE WHEN statement to VARCHAR, right?
WHEN aggrcat = '0' AND botcode='r4' THEN CAST('monitoring' AS VARCHAR)
The common datatype of all branches should then be VARCHAR.
Regards,
Timo
Am 04.02.19 um 11:06
Happy Chinese New Year!
Thank you Jark for working on a prototype and writing up the this great
proposal.
+1 for the suggested approach
Best,
Fabian
Am Mo., 4. Feb. 2019 um 11:05 Uhr schrieb jincheng sun <
sunjincheng...@gmail.com>:
> +1 ， Happy Chinese New Year! :)
>
> Best，Jincheng
> From
+1 ， Happy Chinese New Year! :)
Best，Jincheng
>From Singapore
Jark Wu 于2019年2月4日 周一13:23写道：
> Hi all,
>
> I have drafted the proposal:
>
> https://docs.google.com/document/d/1R1-uDq-KawLB8afQYrczfcoQHjjIhq6tvUksxrfhBl0/edit#
> Please feel free to give any feedbacks!
>
> I have also created a
Hi Ramya,
Fabian and Hequn are partially correct. Return type of `CASE WHEN` statement in
this case should be CHAR(N), with N being the max of the WHEN branches. However
the problem that you are facing is that Flink doesn’t handle CHAR(N) type
correctly. There is an open issue for that:
+1 for the proposal.
Cheers,
Till
On Mon, Feb 4, 2019 at 9:50 AM Robert Metzger wrote:
> Hey Jark,
>
> Happy New Year :)
>
> thanks a lot for the proposal and the prototype. I fully agree with your
> proposal and I think it's good to go!
>
> Regarding the review-bot: We can add another item
Thinking about it I came up that adding a map function after the read is
probably more general.
Is there any "significant" difference in terms of performance in using such
dedicated map function (that just reads a row, increment an accumulator and
returns immediately) vs adding this accumulator
Hi to all,
we often need to track the number of rows of a dataset.
In order to burden on the job complexitye we use accumulators to track this
information.
The problem is that we have to extends all InputFormats that we use in
order to properly handle such row-count accumulator...my question is:
Hey Jark,
Happy New Year :)
thanks a lot for the proposal and the prototype. I fully agree with your
proposal and I think it's good to go!
Regarding the review-bot: We can add another item for documentation in both
English and Chinese, once the framework for the Flink docs has been merged.
On
Hey devs,
I've been only following Flink dev loosely in the last couple of
months and could not find the following information:
What's the schedule for the next release? In particular, when is the
planned feature freeze and when is the planned release date?
I think this can be valuable
12 matches
Mail list logo
