Ying Xu created FLINK-15476:
---
Summary: Update StreamingFileSink documentation -- bulk encoded
writer now supports customized checkpoint policy
Key: FLINK-15476
URL: https://issues.apache.org/jira/browse/FLINK-15476
Rong Rong created FLINK-15475:
-
Summary: Add isOutputTypeUsed() API to Transformation
Key: FLINK-15475
URL: https://issues.apache.org/jira/browse/FLINK-15475
Project: Flink
Issue Type: Improvemen
Aljoscha Krettek created FLINK-15474:
Summary: In TypeSerializerUpgradeTestBase, create serializer
snapshots "on demand"
Key: FLINK-15474
URL: https://issues.apache.org/jira/browse/FLINK-15474
Pro
Hi Timo, Jack,
Well, I added additional column to describe the return type of each
function and
updated the google doc.
Best,
Forward
Jark Wu 于2020年1月3日周五 下午5:48写道：
> Hi Timo,
>
> That's a good point.
> We didn't introduce any new types. We will use the function definition
> defined by Calcite[
Ronald O. Edmark created FLINK-15473:
Summary: Add support for Linux on ppc64le to MemoryArchitecture
Key: FLINK-15473
URL: https://issues.apache.org/jira/browse/FLINK-15473
Project: Flink
godfrey he created FLINK-15472:
--
Summary: Support SQL Client Gateway
Key: FLINK-15472
URL: https://issues.apache.org/jira/browse/FLINK-15472
Project: Flink
Issue Type: New Feature
Com
Chesnay Schepler created FLINK-15471:
Summary: HA e2e check for empty .out files isn't working
Key: FLINK-15471
URL: https://issues.apache.org/jira/browse/FLINK-15471
Project: Flink
Issue
Yang Wang created FLINK-15470:
-
Summary: Remove YARN magic properties file
Key: FLINK-15470
URL: https://issues.apache.org/jira/browse/FLINK-15470
Project: Flink
Issue Type: Task
Compon
Hi Benoît,
Thanks for the reminder. I will look into the issue and hopefully we can
target it into 1.9.2 and 1.10.
Cheers,
Jark
On Fri, 3 Jan 2020 at 18:21, Benoît Paris <
benoit.pa...@centraliens-lille.org> wrote:
> > If anyone finds that blink planner has any significant defects and has
> a
Hi Yu,
Thanks for your great work.
Best,
Vino
Congxian Qiu 于2020年1月3日周五 下午6:18写道：
> Thanks for the great work, and look forward to the first RC.
>
> Best,
> Congxian
>
>
> Jingsong Li 于2020年1月3日周五 下午12:58写道：
>
> > Thanks Yu and Gary,
> >
> > Table and hive layer have resolved all blockers and
Thanks for the great work, and look forward to the first RC.
Best,
Congxian
Jingsong Li 于2020年1月3日周五 下午12:58写道：
> Thanks Yu and Gary,
>
> Table and hive layer have resolved all blockers and critical issues. (38
> blockers and 33 critical issues)
>
> Look forward to the first RC.
>
> Best,
> Ji
Zhenghua Gao created FLINK-15469:
Summary: UpsertStreamTableSink should support new type system
Key: FLINK-15469
URL: https://issues.apache.org/jira/browse/FLINK-15469
Project: Flink
Issue Ty
Hi Timo,
That's a good point.
We didn't introduce any new types. We will use the function definition
defined by Calcite[1].
So all the functions return STRING/BOOLEAN.
Hi Forward,
I think we may need an additional column to describe the return type of
each function.
Best,
Jark
[1]:
https://gith
Hi Timo,
I have the same idea about the two step approach.
+1 to change default planner for Table API in 1.11.
Best,
Jark
On Fri, 3 Jan 2020 at 17:06, Timo Walther wrote:
> Hi Jark,
>
> +1 for making the Blink planner the default planner for the SQL Client.
>
> I think for the Table API, we s
Hi,
sorry for jumping into the discussion so late. I had a quick look at the
FLIP. It looks very nice and detailed. I have one question that I could
not find in the FLIP itself. Maybe it is hidden in the long discussion
thread.
What are the return types of all functions? Do we introduce new
Hi Jark,
+1 for making the Blink planner the default planner for the SQL Client.
I think for the Table API, we should give the planner a bit more
exposure and target the changing of a default planner for 1.11.
What do you think about this two step approach?
Regards,
Timo
On 03.01.20 09:37,
+1, I have already made blink as the default planner of flink interpreter
in Zeppelin
Jingsong Li 于2020年1月3日周五 下午4:37写道：
> Hi Jark,
>
> +1 for default blink planner in SQL-CLI.
> I believe this new planner can be put into practice in production.
> We've worked hard for nearly a year, but the ol
Rui Li created FLINK-15468:
--
Summary: INSERT OVERWRITE not supported from SQL CLI
Key: FLINK-15468
URL: https://issues.apache.org/jira/browse/FLINK-15468
Project: Flink
Issue Type: Bug
Com
ming li created FLINK-15467:
---
Summary: Should wait for the end of the source thread during the
Task cancellation
Key: FLINK-15467
URL: https://issues.apache.org/jira/browse/FLINK-15467
Project: Flink
Hi Jark,
+1 for default blink planner in SQL-CLI.
I believe this new planner can be put into practice in production.
We've worked hard for nearly a year, but the old planner didn't move on.
And I'd like to cc to u...@flink.apache.org.
If anyone finds that blink planner has any significant defects
+1 for this.
We bring many SQL/API features and enhance stability in 1.10 release, and
almost all of them happens in Blink planner.
SQL CLI is the most convenient entrypoint for me, I believe many users will
have a better experience If we set Blink planner as default planner.
Best,
Leonard
> 在
21 matches
Mail list logo
