Hi Caizhi,
Thanks for bringing this up for discussion. I think the important part is
what do developers expect as the default behaviour of a CAST function when
casting fails. If I look at Postgres [1] or MSSQL [2], the default
behaviour of a CAST failing would be to return an error, which would be
Congratulations!
On Thu, 18 Nov 2021 at 02:44, Leonard Xu wrote:
> Congratulations！Yingjie
>
> Best，
> Leonard
>
> > 在 2021年11月18日，01:40，Till Rohrmann 写道：
> >
> > Congratulations Yingjie!
>
>
Hi everyone,
personally I would also prefer the system telling me that something is
wrong instead of silently ignoring records. If there is a TRY_CAST function
that has the old behaviour, people can still get the old behaviour. For
backwards compatibility reasons it is a good idea to introduce a s
Hi,
first of all, thanks for the summary of both sides, and for bringing up the
discussion on this.
I think it is obvious that this is not something we can just "break", so
the config option seems mandatory to me.
Overall I agree with Martijn and Till that throwing errors is the more
expected beh
Yangze Guo created FLINK-24951:
--
Summary: Allow watch bookmarks to mitigate frequent watcher
rebuilding
Key: FLINK-24951
URL: https://issues.apache.org/jira/browse/FLINK-24951
Project: Flink
Is
wangbaohua created FLINK-24952:
--
Summary: Rowtime attributes must not be in the input rows of a
regular join. As a workaround you can cast the time attributes of input tables
to TIMESTAMP before
Key: FLINK-24952
URL
xiangqiao created FLINK-24953:
-
Summary: Optime hive parallelism inference
Key: FLINK-24953
URL: https://issues.apache.org/jira/browse/FLINK-24953
Project: Flink
Issue Type: Improvement
Yingjie Cao created FLINK-24954:
---
Summary: Reset read buffer request timeout on buffer recycling for
sort-shuffle
Key: FLINK-24954
URL: https://issues.apache.org/jira/browse/FLINK-24954
Project: Flink
(added user ML to this thread)
HI all,
I would like to raise a different opinion about this change. I agree with
Ingo that
we should not just break some existing behavior, and even if we introduce an
option to control the behavior, i would propose to set the default value to
current
behavior.
I
Sorry I forgot to add user ML. I also would like to gather some users
feedback on this thing.
Since I didn't get any feedback on this topic before from users.
Best,
Kurt
On Thu, Nov 18, 2021 at 6:33 PM Kurt Young wrote:
> (added user ML to this thread)
>
> HI all,
>
> I would like to raise a d
Congratulations, Yinjie!
Best
Yun Tang
On 2021/11/18 08:01:44 Martijn Visser wrote:
> Congratulations!
>
> On Thu, 18 Nov 2021 at 02:44, Leonard Xu wrote:
>
> > Congratulations！Yingjie
> >
> > Best，
> > Leonard
> >
> > > 在 2021年11月18日，01:40，Till Rohrmann 写道：
> > >
> > > Congratulations Yingji
Hi Joe,
Thanks for bringing this to our attention.
In general, I agreed with Chesnay's reply on PR [1]. For the rule-3, we might
indeed create another PR to add documentation previously. And I think if
forcing to obey it to include the documentation in the same PR, that could
benefit the revie
Hi Wenlong,
Thanks for bringing up this discussion and I believe many guys have ever
suffered from the long and unreadable operator name for long time.
I have another suggestion which inspired by Aitozi, that we could add some hint
to tell the vertex index. Such as make the pipeline from "sourc
Yunfeng Zhou created FLINK-24955:
Summary: Add One-hot Encoder to Flink ML
Key: FLINK-24955
URL: https://issues.apache.org/jira/browse/FLINK-24955
Project: Flink
Issue Type: New Feature
AHeise closed pull request #1:
URL: https://github.com/apache/flink-connectors/pull/1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr
Hi everyone,
thanks for finally have this discussion on the mailing list. As both a
contributor and user, I have experienced a couple issues around
nullability coming out of nowhere in a pipeline. This discussion should
not only cover CAST but failure handling in general.
Let me summarize m
Yuval Itzchakov created FLINK-24956:
---
Summary: SqlSnapshot throws NullPointerException when used in
conjunction with CTE
Key: FLINK-24956
URL: https://issues.apache.org/jira/browse/FLINK-24956
Proje
Hi Timo,
Regarding CAST, I think no one denies the standard behavior which should
raise errors when
failed. The only question is how do we solve it, given lots of users
already relying on current
more tolerant behavior. Some violation of standard but acceptable behavior
doesn't deserve
a breaking
Xianxun Ye created FLINK-24957:
--
Summary: show `host:port` information in `subtasks` tab
Key: FLINK-24957
URL: https://issues.apache.org/jira/browse/FLINK-24957
Project: Flink
Issue Type: Improv
zoucao created FLINK-24958:
--
Summary: correct the example and link for temporal table function
documentation
Key: FLINK-24958
URL: https://issues.apache.org/jira/browse/FLINK-24958
Project: Flink
Congrats and welcome, Yingjie!
Best Regards,
Yu
On Thu, 18 Nov 2021 at 19:01, Yun Tang wrote:
> Congratulations, Yinjie!
>
> Best
> Yun Tang
>
> On 2021/11/18 08:01:44 Martijn Visser wrote:
> > Congratulations!
> >
> > On Thu, 18 Nov 2021 at 02:44, Leonard Xu wrote:
> >
> > > Congratulations！
well deserved! Congratulations, Yingjie!
On Fri, Nov 19, 2021 at 12:39 PM Yu Li wrote:
> Congrats and welcome, Yingjie!
>
> Best Regards,
> Yu
>
>
> On Thu, 18 Nov 2021 at 19:01, Yun Tang wrote:
>
> > Congratulations, Yinjie!
> >
> > Best
> > Yun Tang
> >
> > On 2021/11/18 08:01:44 Martijn Viss
ZhuoYu Chen created FLINK-24959:
---
Summary: Add a BitMap function to FlinkSQL
Key: FLINK-24959
URL: https://issues.apache.org/jira/browse/FLINK-24959
Project: Flink
Issue Type: New Feature
Yun Gao created FLINK-24960:
---
Summary:
YARNSessionCapacitySchedulerITCase.testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots
hangs on azure
Key: FLINK-24960
Hi devs,
I'd like to bring up for a discussion a proposal to clean up ownership
of snapshots, both checkpoints and savepoints.
The goal here is to make it clear who is responsible for deleting
checkpoints/savepoints files and when can that be done in a safe manner.
Looking forward for your feedb
Hi Dawid,
Thanks for working on this FLIP. Clarifying the differences and
guarantees around savepoints and checkpoints will make it easier and safer
for users and downstream projects and platforms to work with them.
+1 to the changing the current (undefined) behavior when recovering from
retained
26 matches
Mail list logo
