Canbin Zheng created FLINK-17565:
Summary: Bump fabric8 version from 4.5.2 to 4.10.1
Key: FLINK-17565
URL: https://issues.apache.org/jira/browse/FLINK-17565
Project: Flink
Issue Type:
Yingjie Cao created FLINK-17564:
---
Summary: Inflight data of incoming channel may be disordered for
unaligned checkpoint
Key: FLINK-17564
URL: https://issues.apache.org/jira/browse/FLINK-17564
Project:
AT-Fieldless created FLINK-17563:
Summary: YARN Setup page has a broken link
Key: FLINK-17563
URL: https://issues.apache.org/jira/browse/FLINK-17563
Project: Flink
Issue Type: Bug
AT-Fieldless created FLINK-17562:
Summary: Monitoring REST API page has duplicate items
Key: FLINK-17562
URL: https://issues.apache.org/jira/browse/FLINK-17562
Project: Flink
Issue Type: Bug
Hi,
I agree what Fabian said above.
Besides, IMO, (3) is in a lower priority and will involve much more things.
It makes sense to me to do it in two-phase.
Regarding to (3), the key point to convert an append-only table into
changelog table is that the framework should know the operation type,
linweijiang created FLINK-17561:
---
Summary: Table program cannot be compiled
Key: FLINK-17561
URL: https://issues.apache.org/jira/browse/FLINK-17561
Project: Flink
Issue Type: Bug
josson paul kalapparambath created FLINK-17560:
--
Summary: No Slots available exception in Apache Flink Job Manager
while Scheduling
Key: FLINK-17560
URL:
Luis created FLINK-17559:
Summary: Backpressure seems to be broken when not going through
network
Key: FLINK-17559
URL: https://issues.apache.org/jira/browse/FLINK-17559
Project: Flink
Issue Type:
Gary Yao created FLINK-17558:
Summary: Partitions are released in TaskExecutor Main Thread
Key: FLINK-17558
URL: https://issues.apache.org/jira/browse/FLINK-17558
Project: Flink
Issue Type: Bug
Thanks for the summary Konstantin.
I think you got all points right.
IMO, the way forward would be to work on a FLIP to define
* the concept of temporal tables,
* how to feed them from retraction tables
* how to feed them from append-only tables
* their specification with CREATE TEMPORAL TABLE,
*
Hi everyone,
Thanks everyone for joining the discussion on this. Please let me summarize
what I have understood so far.
1) For joining an append-only table and a temporal table the syntax the "FOR
SYSTEM_TIME AS OF " seems to be preferred (Fabian, Timo,
Seth).
2) To define a temporal table
Seth Wiesman created FLINK-17557:
Summary: Add configuration to disallow ambiguous file schemes
Key: FLINK-17557
URL: https://issues.apache.org/jira/browse/FLINK-17557
Project: Flink
Issue
Hi everyone,
Please review and vote on the release candidate #3 for version 1.10.1, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
*
Tammy zhang created FLINK-17556:
---
Summary: FATAL: Thread
'flink-metrics-akka.remote.default-remote-dispatcher-3' produced an uncaught
exception. Stopping the process... java.lang.OutOfMemoryError: Direct buffer
memory
Key:
Piotr Nowojski created FLINK-17555:
--
Summary: docstring of
pyflink.table.descriptors.FileSystem:1:duplicate object description of
pyflink.table.descriptors.FileSystem
Key: FLINK-17555
URL:
Till Rohrmann created FLINK-17554:
-
Summary: Add release hooks for user code class loader
Key: FLINK-17554
URL: https://issues.apache.org/jira/browse/FLINK-17554
Project: Flink
Issue Type:
Terry Wang created FLINK-17553:
--
Summary: Group by constant and window causes error: Unsupported
call: TUMBLE_END(TIMESTAMP(3) NOT NULL)
Key: FLINK-17553
URL: https://issues.apache.org/jira/browse/FLINK-17553
Piotr Nowojski created FLINK-17552:
--
Summary: UnionInputGate shouldn't be caching InputChannels
Key: FLINK-17552
URL: https://issues.apache.org/jira/browse/FLINK-17552
Project: Flink
Hi,
There are some feedbacks from @Timo and @Kurt in the voting thread for
FLIP-36 and I want to share my thoughts here.
1. How would the FLIP-36 look like after FLIP-84?
I don't think FLIP-84 will affect FLIP-36 from the public API perspective.
Users can call .cache on a table object and the
Quick update: The .asf.yamls have been committed and we should no longer
see issue and pr notifications coming from flink-web and flink-shaded on
dev@f.a.o. These notifications go now to issues@f.a.o.
Cheers,
Till
On Thu, May 7, 2020 at 8:02 AM Zhu Zhu wrote:
> +1
>
> Thanks,
> Zhu Zhu
>
>
Thanks Yu!
On Thu, May 7, 2020 at 7:44 AM Yu Li wrote:
> @Dawid Yes we will include it into RC3. Thanks for the note.
>
> @Till Thanks for the quick fix and the note.
>
> I've checked and confirmed there are no open issues under 1.10.1, neither
> any resolved/closed ones under 1.10.2, so will
Thanks for the update Godfrey!
+1 to this approach.
Since there can be only one primary key, I'd also be fine to just use `PRI`
even if it is composite, but `PRI(f0, f5)` might be more convenient for
users.
Thanks, Fabian
Am Do., 7. Mai 2020 um 09:31 Uhr schrieb godfrey he :
> Hi fabian,
>
Hi,
Thanks for the feedback, @Timo @Kurt.
I agree that we can postpone the vote after May 15th since the FLIP is not
targeted for Flink 1.11 and the questions you brought up need more
discussion. I prefer moving the discussion back to the discussion thread
and keeping the vote thread clear. I
Hi fabian,
Thanks for you suggestions.
Agree with you that `UNQ(f2, f3)` is more clear.
A table can have only ONE primary key,
this primary key can consist of single or multiple columns. [1]
if primary key consists of single column,
we can simply use `PRI` (or `PRI(xx)`) to represent it.
if
+1
Thanks,
Zhu Zhu
Congxian Qiu 于2020年5月6日周三 下午12:02写道：
> +1 for this
>
> Best,
> Congxian
>
>
> Benchao Li 于2020年5月5日周二 下午5:22写道：
>
> > belated +1
> >
> > Till Rohrmann 于2020年5月5日周二 下午2:24写道：
> >
> > > Thanks for all the feedback. I will open the PRs now which change the
> > > notification
25 matches
Mail list logo
