Alexander Trushev created FLINK-24139:
-
Summary: Push down more predicates through Join in stream mode
Key: FLINK-24139
URL: https://issues.apache.org/jira/browse/FLINK-24139
Project: Flink
Hi Timo, Till,
thanks for your input already. I'm glad to hear that the idea resonates,
also thanks for the additional ideas!
I've created a JIRA issue[1] for now just to track this idea. I'm also
working on a bit of a proof of concept and opened it as a draft PR[2]. I'm
happy for anyone to join
Hi Juha,
Flink does not give backwards compatibility wrt to its internal data
structures. The recommended way is to stop the jobs with a savepoint and
then resume these jobs on the new Flink cluster. Failing over the processes
with a new version is not guaranteed to work atm. I hope this answers y
Ingo Bürk created FLINK-24138:
-
Summary: Automated architectural tests
Key: FLINK-24138
URL: https://issues.apache.org/jira/browse/FLINK-24138
Project: Flink
Issue Type: Improvement
R
Dawid Wysakowicz created FLINK-24137:
Summary: Python tests fail with "Exception in thread
read_grpc_client_inputs"
Key: FLINK-24137
URL: https://issues.apache.org/jira/browse/FLINK-24137
Project:
The migration is pretty much complete and the documentation is now
available at nightlies.apache.org .
Please click around a bit and check if anything is broken.
If no issues are reported by the end of today I will update the links on
the website.
On 01/09/2021 10:11, Chesnay Schepler wrote:
Hello,
I noticed there's a change [1] coming up in Flink 1.14.0 in the ZooKeeper
tree structure ZooKeeper HA services maintains.
I didn't spot any migration logic from the old (< 1.14.0) structure to the
new. Did I miss something?
If you have a Flink cluster running with 1.13.X and let's say add
Hi Zhihao,
Thanks for driving the discussion.
First, I have the same question as Kurt.
Secondly, seamless switching after SQL is upgraded is a complicated topic.
What problems does the system goal of the self-build management system
solve?
Upgrade SQL of a simple ETL job? Upgrade SQL of a compli
Huang Xingbo created FLINK-24136:
Summary:
OverAggregateITCase.testRowTimeBoundedPartitionedRangeOver test failed with NPE
Key: FLINK-24136
URL: https://issues.apache.org/jira/browse/FLINK-24136
Proje
Could you explain why you need a backfill after you take v2 into
production?
Best,
Kurt
On Fri, Sep 3, 2021 at 2:02 AM zhihao wang wrote:
> Hi team
>
> Graceful Application Evolvement is a hard and open problem to the
> community. We met this problem in our production, too. To address it, we
Prakhar Mathur created FLINK-24135:
--
Summary: Add support for metric group tags in StatsDReporter
Key: FLINK-24135
URL: https://issues.apache.org/jira/browse/FLINK-24135
Project: Flink
Issue
Hi team
Graceful Application Evolvement is a hard and open problem to the
community. We met this problem in our production, too. To address it, we
are planning to leverage a backfill-based approach with a self-build
management system. We'd like to learn the community feedback on this
approach.
Ou
Adam Pearce created FLINK-24134:
---
Summary: Docker "Enabling Python" documentation results in failed
Docker builds
Key: FLINK-24134
URL: https://issues.apache.org/jira/browse/FLINK-24134
Project: Flink
Till Rohrmann created FLINK-24133:
-
Summary:
PartitionRequestClientFactoryTest.testThrowsWhenNetworkFailure fails on Azure
Key: FLINK-24133
URL: https://issues.apache.org/jira/browse/FLINK-24133
Proje
Igal Shilman created FLINK-24132:
Summary: directory-maven-plugin fails on Github action
Key: FLINK-24132
URL: https://issues.apache.org/jira/browse/FLINK-24132
Project: Flink
Issue Type: Imp
hi guys when our team developed the business code, we found
ContinuousProcessingTimeTrigger doesn't fire at the end of the window, then I
searched on JIRA, I found this Issue
https://issues.apache.org/jira/plugins/servlet/mobile#issue/FLINK-20443 . I
modified the firing logic so that the wind
Dawid Wysakowicz created FLINK-24131:
Summary: KafkaSinkITCase "Detected producer leak"
Key: FLINK-24131
URL: https://issues.apache.org/jira/browse/FLINK-24131
Project: Flink
Issue Type:
Dawid Wysakowicz created FLINK-24130:
Summary: RowDataSerializerTest fails on Azure
Key: FLINK-24130
URL: https://issues.apache.org/jira/browse/FLINK-24130
Project: Flink
Issue Type: Bug
Till Rohrmann created FLINK-24129:
-
Summary: TopicRangeTest.rangeCreationHaveALimitedScope fails on
Azure
Key: FLINK-24129
URL: https://issues.apache.org/jira/browse/FLINK-24129
Project: Flink
zhuzhengjun created FLINK-24128:
---
Summary: StreamingFileCommiter receive commit message but
checkpoint did't ready
Key: FLINK-24128
URL: https://issues.apache.org/jira/browse/FLINK-24128
Project: Flink
Hi,
I have set up a remote stateful function in python which I’ve deployed
on an AWS EC2 box. I am interacting with this from a separate statefun
docker container running 2 flink-statefun images with roles master and
worker (on a separate EC2 instance). The ingress and egress points for
this funct
Oleg Novoyavchev created FLINK-24127:
Summary: Asynchronous I/O documentation should be updated
Key: FLINK-24127
URL: https://issues.apache.org/jira/browse/FLINK-24127
Project: Flink
Issu
If it is possible to automate these kinds of checks, then I am all for it
because everything else breaks eventually. So +1 for this proposal.
I don't have experience with what tools are available, though.
I would like to add a rule that every test class extends directly or
indirectly TestLogger b
Hi Ingo,
thanks for starting this discussion. Having more automation is
definitely desirable. Esp. in the API / SDK areas where we frequently
have to add similar comments to PRs. The more checks the better. We
definitely also need more guidelines (e.g. how to develop a Flink
connector) but au
Qingsheng Ren created FLINK-24126:
-
Summary: Use increment of bytes-consumed-total for updating
numBytesIn in KafkaSource
Key: FLINK-24126
URL: https://issues.apache.org/jira/browse/FLINK-24126
Projec
Chesnay Schepler created FLINK-24125:
Summary: Rethink relationship between DeclarativeSlotPool and
*Bridge
Key: FLINK-24125
URL: https://issues.apache.org/jira/browse/FLINK-24125
Project: Flink
Aitozi created FLINK-24124:
--
Summary: Use explicit pool size to construct thread pool instead
of Hardware.getNumberCPUCores()
Key: FLINK-24124
URL: https://issues.apache.org/jira/browse/FLINK-24124
Project:
27 matches
Mail list logo