Wei-Che Wei created FLINK-22970:
---
Summary: The documentation for `TO_TIMESTAMP` UDF has an incorrect
description
Key: FLINK-22970
URL: https://issues.apache.org/jira/browse/FLINK-22970
Project: Flink
Thanks for all the discussions and suggestions. Since the topic has
been discussed for about a week, it is time to have a conclusion and new
ideas are welcomed at the same time.
First, the topic starts with use cases in restful interface. The
restful interface supported many useful
Shengkai Fang created FLINK-22969:
-
Summary: Validate the topic is not null or empty string when
create kafka source/sink function
Key: FLINK-22969
URL: https://issues.apache.org/jira/browse/FLINK-22969
Hello,
Could someone help me to advance the jira
FLINK-22885(https://issues.apache.org/jira/browse/FLINK-22885)? It has been at
standstill for some time.
Thank you.
Best,
Roc.
Hi Lu,
Xintong has a professional analysis about TM heartbeat timeout in a
historical mail[1], please check if it could help.
[1]
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Heartbeat-of-TaskManager-timed-out-td36228.html
Best regards,
JING ZHANG
Lu Niu 于2021年6月11日周五
DaChun created FLINK-22968:
--
Summary: String type cannot be used when creating Flink SQL
Key: FLINK-22968
URL: https://issues.apache.org/jira/browse/FLINK-22968
Project: Flink
Issue Type: Bug
I quickly updated the draft PR that would propagate idleness information to
the Sink function, based on the recent improvement provided by
FLINK-18934. For illustration purposes.
https://github.com/streamnative/flink/pull/2
On Thu, Jun 10, 2021 at 11:34 AM Eron Wright
wrote:
> Regarding
Maciej Bryński created FLINK-22967:
--
Summary: CodeGenException: Unsupported cast for nested Decimals
Key: FLINK-22967
URL: https://issues.apache.org/jira/browse/FLINK-22967
Project: Flink
Regarding records vs watermarks, I feel it is wrong to include records in
the considerations, because the clearest definition of idleness (IMO) is
'active participation in advancing the event-time clock', and records don't
directly affect the clock. Of course, records indirectly influence the
Hi, Flink User
Several of our applications get heartbeat timeout occasionally. there is no
GC, no OOM:
```
- realtime conversion event filter (49/120)
(16e3d3e7608eed0a30e0508eb52065fd) switched from RUNNING to FAILED on
container_e05_1599158866703_129001_01_000111 @
Roman Khachatryan created FLINK-22966:
-
Summary: NPE in StateAssignmentOperation when rescaling
Key: FLINK-22966
URL: https://issues.apache.org/jira/browse/FLINK-22966
Project: Flink
We have 7 binding votes and no objections, so FLIP-167 passed.
Here's the implementation issue and PR which is ready for review.
https://issues.apache.org/jira/browse/FLINK-22700
https://github.com/apache/flink/pull/15950
Thank-you everyone.
On Thu, Jun 10, 2021 at 3:32 AM Arvid Heise wrote:
Bhagi created FLINK-22965:
-
Summary: Association with remote system has failed, address is now
gated
Key: FLINK-22965
URL: https://issues.apache.org/jira/browse/FLINK-22965
Project: Flink
Issue
Arvid Heise created FLINK-22964:
---
Summary: Connector-base exposes dependency to flink-core.
Key: FLINK-22964
URL: https://issues.apache.org/jira/browse/FLINK-22964
Project: Flink
Issue Type:
JasonLee created FLINK-22963:
Summary: The description of taskmanager.memory.task.heap.size in
the official document is incorrect
Key: FLINK-22963
URL: https://issues.apache.org/jira/browse/FLINK-22963
Prateek Kohli created FLINK-22962:
-
Summary: Key group is not in KeyGroupRange error while
checkpointing
Key: FLINK-22962
URL: https://issues.apache.org/jira/browse/FLINK-22962
Project: Flink
Hello everyone,
we would like to pick up work on FLIP-129 which aims to improve the Table
API by supporting the creation of sources / sinks without having to go
through SQL/DDL. This FLIP was approved a while ago, and some things have
changed since then. We'd like to propose a few changes, see
Hi,
fair enough, sorry for the misunderstanding. I'll start a new DISCUSS
thread. Thanks for showing me the way!
Regards
Ingo
On Thu, Jun 10, 2021 at 1:37 PM Timo Walther wrote:
> Hi Ingo,
>
> thanks for giving FLIP-129 an update before finally implementing it. I
> wouldn't start with a
Hi Ingo,
thanks for giving FLIP-129 an update before finally implementing it. I
wouldn't start with a voting thread right away but collect more feedback
from the community in a [DISCUSS] thread before.
Also, voting threads should be performed on the updated wiki page and
include the voting
Anton Kalashnikov created FLINK-22961:
-
Summary: Incorrect calculation of alignment timeout for
LocalInputChannel
Key: FLINK-22961
URL: https://issues.apache.org/jira/browse/FLINK-22961
Project:
Reconfirming my +1 (binding).
On Thu, Jun 10, 2021 at 12:14 PM Till Rohrmann wrote:
> +1,
>
> Cheers,
> Till
>
> On Thu, Jun 10, 2021 at 4:59 AM Tzu-Li (Gordon) Tai
> wrote:
>
> > +1
> >
> > On Thu, Jun 10, 2021 at 9:04 AM jincheng sun
> > wrote:
> >
> > > +1 (binding) // Sorry for the late
Thanks for providing these details Gordon. I have to admit that I do not
fully follow the reasoning why periodic watermark generators forced us to
define idleness for records. Is it because the idleness was generated based
on the non-availability of more data in the sources and not in the
+1,
Cheers,
Till
On Thu, Jun 10, 2021 at 4:59 AM Tzu-Li (Gordon) Tai
wrote:
> +1
>
> On Thu, Jun 10, 2021 at 9:04 AM jincheng sun
> wrote:
>
> > +1 (binding) // Sorry for the late reply.
> >
> > Best,
> > Jincheng
> >
> >
> > Piotr Nowojski 于2021年6月9日周三 下午10:04写道：
> >
> > > Thanks for
Hello everyone,
we would like to pick up work on FLIP-129 which aims to improve the Table
API by supporting the creation of sources / sinks without having to go
through SQL/DDL. This FLIP was approved a while ago, and some things have
changed since then. We'd like to propose a few changes, see
Jingsong Lee created FLINK-22960:
Summary: Temporal join TTL should use enableTimeToLive of state
instead of timer
Key: FLINK-22960
URL: https://issues.apache.org/jira/browse/FLINK-22960
Project:
lukehua created FLINK-22959:
---
Summary: Keep the job jar files on JobManager
Key: FLINK-22959
URL: https://issues.apache.org/jira/browse/FLINK-22959
Project: Flink
Issue Type: Improvement
Hey Piotrek,
Thanks for your comments on the FLIP. I'll address your second question first,
as I think it's more central to this FLIP. Just looking at the AWS ecosystem,
there are several sinks with overlapping functionality. I've chosen AWS sinks
here because I'm most familiar with those, but
+1 to what Arvid said.
I am also thinking we could even consider dropping the dispose method
straightaway to make the need for migration obvious. I'd make that
decision during the implementation/on the PR though, once we verify if
the deprecation option works.
Best,
Dawid
On 10/06/2021 09:37,
The whole operator API is only for advanced users and is not marked
Public(Evolving). Users have to accept that things change and we have to
use that freedom that we don't have in many other parts of the system.
The change needs to be very clear in the change notes though. I also don't
expect
Hi Yangze,
Thanks for incorporating the ideas and sorry for missing the builder part.
My main idea is that SlotSharingGroup is immutable, such that the user
doesn't do:
ssg = new SlotSharingGroup();
ssg.setCpus(2);
operator1.slotSharingGroup(ssg);
ssg.setCpus(4);
operator2.slotSharingGroup(ssg);
Ingo Bürk created FLINK-22958:
-
Summary: Reused content in docs causes confusing navigation jumps
Key: FLINK-22958
URL: https://issues.apache.org/jira/browse/FLINK-22958
Project: Flink
Issue
Hi all,
Very thanks for the warm discussions!
Regarding the change in the operator lifecycle, I also agree with adding
the flush/drain/stopAndFlush/finish method. For the duplication between this
method and `endInput` for one input operator, with some offline disucssion with
Dawid now I also
32 matches
Mail list logo
