jinhai created FLINK-17203:
--
Summary: Add metrics for ClickHouse sink
Key: FLINK-17203
URL: https://issues.apache.org/jira/browse/FLINK-17203
Project: Flink
Issue Type: New Feature
jinhai created FLINK-17202:
--
Summary: Add SQL for ClickHouse connector
Key: FLINK-17202
URL: https://issues.apache.org/jira/browse/FLINK-17202
Project: Flink
Issue Type: New Feature
jinhai created FLINK-17201:
--
Summary: Implement Streaming ClickHouseSink
Key: FLINK-17201
URL: https://issues.apache.org/jira/browse/FLINK-17201
Project: Flink
Issue Type: New Feature
jinhai created FLINK-17200:
--
Summary: Add connectors to ClickHouse
Key: FLINK-17200
URL: https://issues.apache.org/jira/browse/FLINK-17200
Project: Flink
Issue Type: New Feature
Thanks for proposing this improvement, Yangze.
+1 (binding)
Thanks,
Zhu Zhu
Zhijiang 于2020年4月17日周五 下午12:36写道：
> Thanks for this FLIP, Yangze.
>
> Sorry for not involving in the previous discussion. In general I like the
> proposed direction to make related IDs have more rich information for
>
Benchao Li created FLINK-17199:
--
Summary: Use NeverReturnExpired strategy for states in blink
streaming join.
Key: FLINK-17199
URL: https://issues.apache.org/jira/browse/FLINK-17199
Project: Flink
To keep the VOTE thread clean, I just forward @Zhijiang 's reminder here:
> Sorry for not involving in the previous discussion. In general I like the
> proposed direction to make related IDs have more rich information for
> debugging and correlation.
> But I have a bit reminder for the
Hi Konstantin,
Thanks for bringing this discussion. I think temporal join is a very
important feature and should be exposed to pure SQL users.
And I already received many requirements like this.
However, my concern is that how to properly support this feature in SQL.
Introducing a DDL syntax for
Thanks for this FLIP, Yangze.
Sorry for not involving in the previous discussion. In general I like the
proposed direction to make related IDs have more rich information for debugging
and correlation.
But I have a bit reminder for the changes. After failover restarting, every
related IDs
Rui Li created FLINK-17198:
--
Summary: DDL and DML compatibility for Hive connector
Key: FLINK-17198
URL: https://issues.apache.org/jira/browse/FLINK-17198
Project: Flink
Issue Type: New Feature
Caizhi Weng created FLINK-17197:
---
Summary: ContinuousFileReaderOperator might shade the real
exception when processing records
Key: FLINK-17197
URL: https://issues.apache.org/jira/browse/FLINK-17197
Hi,
I like the idea of web tool to assemble fat distribution. And the
https://code.quarkus.io/ looks very nice.
All the users need to do is just select what he/she need (I think this step
can't be omitted anyway).
We can also provide a default fat distribution on the web which default
selects
Canbin Zheng created FLINK-17196:
Summary: Rework the implementation of
Fabric8FlinkKubeClient#getRestEndpoint
Key: FLINK-17196
URL: https://issues.apache.org/jira/browse/FLINK-17196
Project: Flink
Teng Fei Liao created FLINK-17195:
-
Summary: Worker threads for source function have wrong ClassLoader
Key: FLINK-17195
URL: https://issues.apache.org/jira/browse/FLINK-17195
Project: Flink
Hi all,
All the blocker issues for 1.9.3 have been resolved and I'm preparing the first
RC now.
Thanks,
Dian
> 在 2020年4月15日，下午10:27，Dian Fu 写道：
>
> Thanks you all for the positive feedback and thanks a lot Congxian and Yu for
> working on FLINK-16576.
>
> I'll create the first RC after
Chesnay Schepler created FLINK-17194:
Summary: TPC-DS end-to-end test fails due to missing execution
attempt
Key: FLINK-17194
URL: https://issues.apache.org/jira/browse/FLINK-17194
Project: Flink
Rafi Aroch created FLINK-17193:
--
Summary: k8s-python-example build-example.sh improvements
Key: FLINK-17193
URL: https://issues.apache.org/jira/browse/FLINK-17193
Project: Flink
Issue Type:
As a reference for a nice first-experience I had, take a look at
https://code.quarkus.io/
You reach this page after you click "Start Coding" at the project homepage.
Rafi
On Thu, Apr 16, 2020 at 6:53 PM Kurt Young wrote:
> I'm not saying pre-bundle some jars will make this problem go away,
I'm not saying pre-bundle some jars will make this problem go away, and
you're right that only hides the problem for
some users. But what if this solution can hide the problem for 90% users?
Would't that be good enough for us to try?
Regarding to would users following instructions really be such
Thanks for the efforts and feedbacks all.
Now the only left blocker is the below one (newly escalated with a solid
reason), will create RC1 right after it's resolved.
FLINK-16662 Blink Planner failed to generate JobGraph for POJO DataStream
converting to Table (Cannot determine simple type name)
The problem with having a distribution with "popular" stuff is that it
doesn't really /solve/ a problem, it just hides it for users who fall
into these particular use-cases.
Move out of it and you once again run into exact same problems out-lined.
This is exactly why I like the tooling
Hi Konstantin,
Thanks for bringing up this discussion. +1 for the idea.
We have met this in our company too, and I planned to support it recently
in our internal branch.
regarding to your questions,
1) I think it might be more a table/view than function, just like Temporal
Table (which is also
I'm not so sure about the web tool solution though. The concern I have for
this approach is the final generated
distribution is kind of non-deterministic. We might generate too many
different combinations when user trying to
package different types of connector, format, and even maybe hadoop
Hi,
Apparently the IDEs (like IntelliJ) are imperfect at supporting the DEVs in
these kinds of use cases.
The solutions you see are like you have in IntelliJ: a "generate-sources"
button.
It is a way of working I see in almost all projects I'm involved with:
Almost all either use a parser
Thanks for creating this FLIP, Yangze.
+1 (binding).
Cheers,
Till
On Thu, Apr 16, 2020 at 10:51 AM Yangze Guo wrote:
> Hi everyone,
>
> I'd like to start the vote of FLIP-118 [1], which improves the log
> readability by adding more information to Flink’s IDs. This FLIP is
> discussed in the
Hi all,
The voting for FLIP-123 has been over 72h and there're 3 binding +1 votes
from:
- Kurt,
- Jingsong Li,
- Rong Rong
There's no disapproval vote.
Therefore the vote is closed and FLIP-123 has been accepted.
Thanks everyone for the help with review and vote for this FLIP.
On Wed, Apr 15,
I think what Chesnay and Dawid proposed would be the ideal solution.
Ideally, we would also have a nice web tool for the website which generates
the corresponding distribution for download.
To get things started we could start with only supporting to
download/creating the "fat" version with the
Dawid Wysakowicz created FLINK-17191:
Summary: CREATE TABLE does not support interval types
Key: FLINK-17191
URL: https://issues.apache.org/jira/browse/FLINK-17191
Project: Flink
Issue
+1 (binding)
Thanks,
Timo
On 16.04.20 11:32, Benchao Li wrote:
+1 (non-binding)
Aljoscha Krettek 于2020年4月16日周四 下午5:10写道：
+1 (binding)
Aljoscha
Timo Walther created FLINK-17190:
Summary: SQL client does not support views that reference a table
from DDL
Key: FLINK-17190
URL: https://issues.apache.org/jira/browse/FLINK-17190
Project: Flink
Dawid Wysakowicz created FLINK-17188:
Summary: Failed to download conda when running python tests
Key: FLINK-17188
URL: https://issues.apache.org/jira/browse/FLINK-17188
Project: Flink
Thanks a lot for driving this, Yu! Looking forward to the first RC of 1.10.1
FLINK-16576 has been merged into release-1.10 already.
Best,
Congxian
Dian Fu 于2020年4月16日周四 上午10:35写道：
> Thanks a lot for driving this, Yu! Looking forward for the first RC of
> 1.10.1.
>
> > 在
Hi everyone,
it would be very useful if temporal tables could be created via DDL.
Currently, users either need to do this in the Table API or in the
environment file of the Flink CLI, which both require the user to switch
the context of the SQL CLI/Editor. I recently created a ticket for this
Chesnay Schepler created FLINK-17187:
Summary: Streamline setting of config options
Key: FLINK-17187
URL: https://issues.apache.org/jira/browse/FLINK-17187
Project: Flink
Issue Type:
jiefeng zheng created FLINK-17186:
-
Summary: set eventtime from source with timestampsFromField
funcation at flink 1.10 error
Key: FLINK-17186
URL: https://issues.apache.org/jira/browse/FLINK-17186
zck created FLINK-17185:
---
Summary: blink执行计划，自定义函数解析 array，参数为空元素
Key: FLINK-17185
URL: https://issues.apache.org/jira/browse/FLINK-17185
Project: Flink
Issue Type: Bug
Components: Table SQL
zck created FLINK-17184:
---
Summary: sink_ddl source_ddl query_sql webui没有指标数据
Key: FLINK-17184
URL: https://issues.apache.org/jira/browse/FLINK-17184
Project: Flink
Issue Type: Bug
Hi all,
Few points from my side:
1. I like the idea of simplifying the experience for first time users.
As for production use cases I share Jark's opinion that in this case I
would expect users to combine their distribution manually. I think in
such scenarios it is important to understand
+1 (non-binding)
Aljoscha Krettek 于2020年4月16日周四 下午5:10写道：
> +1 (binding)
>
> Aljoscha
>
--
Benchao Li
School of Electronics Engineering and Computer Science, Peking University
Tel:+86-15650713730
Email: libenc...@gmail.com; libenc...@pku.edu.cn
muzimusi created FLINK-17183:
Summary: the 'create table [if not exists]' syntax is not supported
Key: FLINK-17183
URL: https://issues.apache.org/jira/browse/FLINK-17183
Project: Flink
Issue
+1 (binding)
Aljoscha
Thanks a lot for driving this, Yu!
Some users are already asking "where to download release-1.10.1?"
Looking forward to the rc.
Best,
Godfrey
Hequn Cheng 于2020年4月16日周四 下午12:45写道：
> Thanks a lot for your great work Yu! Looking forward to the RC.
>
> Best, Hequn
>
> On Thu, Apr 16, 2020 at 10:35
I want to reinforce my opinion from earlier: This is about improving the
situation both for first-time users and for experienced users that want
to use a Flink dist in production. The current Flink dist is too "thin"
for first-time SQL users and it is too "fat" for production users, that
is
I'd be very happy if someone took over that part of the documentation!
There are open issues for the TODOs in the concepts section here:
https://issues.apache.org/jira/browse/FLINK-12639. But feel free to
comment there/close/re-arrange as you see fit. Maybe we use this thread
and Jira to
> I am happy to get the repo created for you.
Thank you, @seth. I think we are also going to want a new flink-training
component in Jira. Maybe you can help there too?
> If we go with the documentation (vs flink.apache.org) do you think we
> should remove any of the existing content? There is
Hi everyone,
I'd like to start the vote of FLIP-118 [1], which improves the log
readability by adding more information to Flink’s IDs. This FLIP is
discussed in the thread[2].
The vote will be open for at least 72 hours. Unless there is an objection,
I will try to close it by April 21, 2020
+1 (binding)
Thanks Dawid for driving this.
Best,
Jark
On Thu, 16 Apr 2020 at 15:54, Dawid Wysakowicz
wrote:
> Hi all,
>
> I would like to start the vote for FLIP-124 [1], which is discussed and
> reached a consensus in the discussion thread [2].
>
> The vote will be open until April 20th,
Hi all,
I would like to start the vote for FLIP-124 [1], which is discussed and
reached a consensus in the discussion thread [2].
The vote will be open until April 20th, unless there is an objection or
not enough votes.
Best,
Dawid
[1]
Dawid Wysakowicz created FLINK-17182:
Summary:
RemoteInputChannelTest.testConcurrentOnSenderBacklogAndRecycle fail on azure
Key: FLINK-17182
URL: https://issues.apache.org/jira/browse/FLINK-17182
Gary Yao created FLINK-17181:
Summary: Simplify generic Types in Topology Interface
Key: FLINK-17181
URL: https://issues.apache.org/jira/browse/FLINK-17181
Project: Flink
Issue Type: Sub-task
Gary Yao created FLINK-17180:
Summary: Implement PipelinedRegion interface for SchedulingTopology
Key: FLINK-17180
URL: https://issues.apache.org/jira/browse/FLINK-17180
Project: Flink
Issue
Yiwen Tu created FLINK-17179:
Summary: Set row time attribute not working in connector descriptor
Key: FLINK-17179
URL: https://issues.apache.org/jira/browse/FLINK-17179
Project: Flink
Issue
Lijie Wang created FLINK-17178:
--
Summary: Provide "ALL" cache strategy in LookupFunction
Key: FLINK-17178
URL: https://issues.apache.org/jira/browse/FLINK-17178
Project: Flink
Issue Type: New
Canbin Zheng created FLINK-17177:
Summary: Handle Pod ERROR event correctly in
KubernetesResourceManager#onError
Key: FLINK-17177
URL: https://issues.apache.org/jira/browse/FLINK-17177
Project: Flink
Canbin Zheng created FLINK-17176:
Summary: Slow down Pod recreation in
KubernetesResourceManager#PodCallbackHandler
Key: FLINK-17176
URL: https://issues.apache.org/jira/browse/FLINK-17176
Project:
55 matches
Mail list logo
