Dawid Wysakowicz created FLINK-22708:
Summary: Propagate savepoint settings from
StreamExecutionEnvironment to StreamGraph
Key: FLINK-22708
URL: https://issues.apache.org/jira/browse/FLINK-22708
P
Timo Walther created FLINK-22709:
Summary: Drop usages of EnvironmentSettings.useOldPlanner()
Key: FLINK-22709
URL: https://issues.apache.org/jira/browse/FLINK-22709
Project: Flink
Issue Type
Guowei Ma created FLINK-22710:
-
Summary:
ParquetProtoStreamingFileSinkITCase.testParquetProtoWriters failed
Key: FLINK-22710
URL: https://issues.apache.org/jira/browse/FLINK-22710
Project: Flink
Hi Eron,
Thanks for pushing that topic. I can now see that the benefit is even
bigger than I initially thought. So it's worthwhile anyways to include that.
I also briefly thought about exposing watermarks to all UDFs, but here I
really have an issue to see specific use cases. Could you maybe take
zlzhang0122 created FLINK-22711:
---
Summary: NoClassDefFoundError when running Flink 1.11.1 in
openJDK8u292-b10
Key: FLINK-22711
URL: https://issues.apache.org/jira/browse/FLINK-22711
Project: Flink
Dear devs,
In the last couple of weeks, I have noticed that we are slacking a bit on
the components in PR/commit messages. I'd like to gather some feedback if
we still want to include them and if so, how we can improve the process of
finding the correct label.
My personal opinion: So far, I have
For commit messages the labels are useful mostly when scanning the
commit history, like searching for some commit that could've caused
something /without knowing where that change was made/, because it
enables you to quickly filter out commits by their label instead of
having to read the entire
Huang Xingbo created FLINK-22712:
Summary: Support accessing Row fields by attribute name in PyFlink
Row-based Operation
Key: FLINK-22712
URL: https://issues.apache.org/jira/browse/FLINK-22712
Project
I think a big problem with the component labels is that there is
a) no defined set of labels
b) no way to enforce the usage of them
c) no easy way to figure out which label to use
Due to these problems they are used very inconsistently in the project.
I do agree with Arvid's observation that the
weizheng created FLINK-22713:
Summary: Correct grammatical mistakes in 'Kafka' page of
'DataStream Connectors'
Key: FLINK-22713
URL: https://issues.apache.org/jira/browse/FLINK-22713
Project: Flink
+1 (binding)
- checked repository contents
- reviewed flink-web PR
On 5/17/2021 11:40 AM, Xingbo Huang wrote:
+1 (non-binding)
- Verified checksums and signatures
- Check python package contents
- Pip install python wheel package
- Run python udf job in python shell
Best,
Xingbo
Robert Metzg
Hi everyone,
As you might have noticed, the Flink Jira Bot has been offline for two
weeks or so, because it created too much load on the email notification
system.
It has been reactivated now, and is limited to 100 ticket updates per run.
Additionally, you should now only receive one notification
Hi everyone,
Till and I recently discussed whether we should disable the
"stale-blocker", "stale-critical", "stale-major" and "stale-minor" rules
for tickets that have a fixVersion set. This would allow people to plan the
upcoming release without tickets being deprioritized by the bot during the
r
I like this idea. +1 for your proposal Konstantin.
Cheers,
Till
On Wed, May 19, 2021 at 1:30 PM Konstantin Knauf
wrote:
> Hi everyone,
>
> Till and I recently discussed whether we should disable the
> "stale-blocker", "stale-critical", "stale-major" and "stale-minor" rules
> for tickets that ha
Andy created FLINK-22714:
Summary: Simplify `StreamPhysicalWindowTableFunction` to
`StreamPhysicalWindowAssignerFunction` which is only a simple window assigner
table function if successor node with `WindowAttachedWindowingStrategy` in
planner
Andy created FLINK-22715:
Summary: Implement streaming window assigner tablefunction operator
Key: FLINK-22715
URL: https://issues.apache.org/jira/browse/FLINK-22715
Project: Flink
Issue Type: Sub-ta
tartarus created FLINK-22716:
Summary: Add metrics watermarkAlignedChannelNum
Key: FLINK-22716
URL: https://issues.apache.org/jira/browse/FLINK-22716
Project: Flink
Issue Type: Improvement
Roman Khachatryan created FLINK-22717:
-
Summary:
JobMasterStopWithSavepointITCase.testRestartCheckpointCoordinatorIfStopWithSavepointFails
fails with Adaptive Scheduler
Key: FLINK-22717
URL: https://issues.ap
Hi Arvid and Eron,
Thanks for the discussion and I read through Eron's pull request and I think
this can benefit Pravega Flink connector as well.
Here is some background. Pravega had the watermark concept through the event
stream since two years ago, and here is a blog introduction[1] for Prave
HYUNHOO KWON created FLINK-22718:
Summary: java.lang.Exception: Could not create actor system
Key: FLINK-22718
URL: https://issues.apache.org/jira/browse/FLINK-22718
Project: Flink
Issue Type
Jingsong Lee created FLINK-22719:
Summary: WindowJoinUtil.containsWindowStartEqualityAndEndEquality
should not throw exception
Key: FLINK-22719
URL: https://issues.apache.org/jira/browse/FLINK-22719
P
+1 (non-binding)
- verified signatures and hashes
- started a cluster, WebUI was accessible
- ran some queries in SQL Client, no suspicious log output
- the web PR looks good
Best,
Leonard Xu
> 在 2021年5月19日，18:42，Chesnay Schepler 写道：
>
> +1 (binding)
>
> - checked repository contents
> - revi
Guowei Ma created FLINK-22720:
-
Summary: UpsertKafkaTableITCase.testAggregate fail due to
ConcurrentModificationException
Key: FLINK-22720
URL: https://issues.apache.org/jira/browse/FLINK-22720
Project: F
+1 (binding)
- built from source
- run internal tests
- run job on provided convenience binaries
Thanks for managing the release, Arvid!
On Wed, May 19, 2021 at 9:36 PM Leonard Xu wrote:
> +1 (non-binding)
>
> - verified signatures and hashes
> - started a cluster, WebUI was accessible
> - ra
24 matches
Mail list logo
