Dong Lin created FLINK-22488:
Summary: KafkaSourceLegacyITCase.testOneToOneSources failed due to
"OperatorEvent from an OperatorCoordinator to a task was lost"
Key: FLINK-22488
URL: https://issues.apache.org/jira/brow
Huang Xingbo created FLINK-22487:
Summary: Support `print` to print logs in PyFlink
Key: FLINK-22487
URL: https://issues.apache.org/jira/browse/FLINK-22487
Project: Flink
Issue Type: New Feat
Shengkai Fang created FLINK-22486:
-
Summary: Wrong results of the IN operator
Key: FLINK-22486
URL: https://issues.apache.org/jira/browse/FLINK-22486
Project: Flink
Issue Type: Bug
Junfan Zhang created FLINK-22485:
Summary: Support client attach on application mode
Key: FLINK-22485
URL: https://issues.apache.org/jira/browse/FLINK-22485
Project: Flink
Issue Type: Improve
I was actually recently wondering if we shouldn't rather use timeouts more
aggressively in JUnit.
There was recently a case where a number of tests accidentally ran for 5
minutes, because a timeout was increased to 5 minutes.
If we had a global limit of 1 minute per test, we would have caught this
Hi Sonam,
sorry for the late reply. We were a bit caught in the midst of the feature
freeze for the next major Flink release.
In general, I think it is a very good idea to disaggregate the local state
storage to make it reusable across TaskManager failures. However, it is
also not trivial to do.
Sergey Nuyanzin created FLINK-22484:
---
Summary: Buit-in functions for collections
Key: FLINK-22484
URL: https://issues.apache.org/jira/browse/FLINK-22484
Project: Flink
Issue Type: Sub-task
Robert Metzger created FLINK-22483:
--
Summary: Recover checkpoints when JobMaster gains leadership
Key: FLINK-22483
URL: https://issues.apache.org/jira/browse/FLINK-22483
Project: Flink
Issue
Dawid Wysakowicz created FLINK-22482:
Summary: ParquetFileSystemITCase fails on Azure
Key: FLINK-22482
URL: https://issues.apache.org/jira/browse/FLINK-22482
Project: Flink
Issue Type: Bu
Dawid Wysakowicz created FLINK-22481:
Summary: RocksDBStateBackendWindowITCase times out on Azure
Key: FLINK-22481
URL: https://issues.apache.org/jira/browse/FLINK-22481
Project: Flink
Is
Dawid Wysakowicz created FLINK-22480:
Summary: KafkaChangelogTableITCase hangs on Azure
Key: FLINK-22480
URL: https://issues.apache.org/jira/browse/FLINK-22480
Project: Flink
Issue Type:
Hi folks,
I am writing to your project list as there have been submissions from your
project to the IoT track in the past, we have integration modules for your
project in PLC4X, you are listed as "IoT" category project, or I just thought
your project would be a good match for an IoT related tal
Danny Cranmer created FLINK-22479:
-
Summary: [Kinesis][Consumer] Potential lock-up under error
condition
Key: FLINK-22479
URL: https://issues.apache.org/jira/browse/FLINK-22479
Project: Flink
Lars Bachmann created FLINK-22478:
-
Summary: confluent schema registry avro (de)serialization https
support
Key: FLINK-22478
URL: https://issues.apache.org/jira/browse/FLINK-22478
Project: Flink
Till Rohrmann created FLINK-22477:
-
Summary: Remove DefaultSlotPoolServiceFactory and SlotPoolImpl
Key: FLINK-22477
URL: https://issues.apache.org/jira/browse/FLINK-22477
Project: Flink
Issue
Hi Till,
I have created the ticket to extend the description of `execution.targe`.
https://issues.apache.org/jira/browse/FLINK-22476
best regards,
Tony Wei 於 2021年4月26日 週一 下午5:24寫道:
> Hi Till, Yangze,
>
> I think FLINK-15852 should solve my problem.
> It is my fault that my flink version is no
Wei-Che Wei created FLINK-22476:
---
Summary: Extend the description of the config option
`execution.target`
Key: FLINK-22476
URL: https://issues.apache.org/jira/browse/FLINK-22476
Project: Flink
Hi Till, Yangze,
I think FLINK-15852 should solve my problem.
It is my fault that my flink version is not 100% consistent with the
community version, and FLINK-15852 is the one I missed.
Thanks for your information.
best regards,
Till Rohrmann 於 2021年4月26日 週一 下午5:14寫道:
> I think you are right
If the GenericCLI is selected, then the execution.target should have
been overwritten to "yarn-application" in GenericCLI#toConfiguration.
It is odd that why the GenericCLI#isActive return false as the
execution.target is defined in both flink-conf and command line.
Best,
Yangze Guo
On Mon, Apr 2
I think you are right that the `GenericCLI` should be the first choice.
>From the top of my head I do not remember why FlinkYarnSessionCli is still
used. Maybe it is in order to support some Yarn specific cli option
parsing. I assume it is either an oversight or some parsing has not been
completely
Hi, Till,
I agree that we need to resolve the issue by overriding the
configuration before selecting the CustomCommandLines. However, IIUC,
after FLINK-15852 the GenericCLI should always be the first choice.
Could you help me to understand why the FlinkYarnSessionCli can be
activated?
Best,
Yang
+1. I think this rule makes a lot of sense.
Cheers,
Till
On Mon, Apr 26, 2021 at 10:08 AM Arvid Heise wrote:
> +1 from my side.
>
> We should probably double-check if we really need 4h timeouts on test tasks
> in AZP. It feels like 2h be enough.
>
> On Mon, Apr 26, 2021 at 9:54 AM Dawid Wysakow
Hi Tony,
I think you are right that Flink's cli does not behave super consistent at
the moment. Case 2. should definitely work because `-t yarn-application`
should overwrite what is defined in the Flink configuration. The problem
seems to be that we don't resolve the configuration wrt the specifie
+1 from my side.
We should probably double-check if we really need 4h timeouts on test tasks
in AZP. It feels like 2h be enough.
On Mon, Apr 26, 2021 at 9:54 AM Dawid Wysakowicz
wrote:
> Hi devs!
>
> I wanted to bring up something that was discussed in a few independent
> groups of people in th
Hi devs!
I wanted to bring up something that was discussed in a few independent
groups of people in the past days. I'd like to revise using timeouts in
our JUnit tests. The suggestion would be not to use them anymore. The
problem with timeouts is that we have no thread dump and stack traces of
the
Ingo Bürk created FLINK-22475:
-
Summary: Datagen connector does not list its available options
with placeholders
Key: FLINK-22475
URL: https://issues.apache.org/jira/browse/FLINK-22475
Project: Flink
Till Rohrmann created FLINK-22474:
-
Summary: Display job configuration in web-ui
Key: FLINK-22474
URL: https://issues.apache.org/jira/browse/FLINK-22474
Project: Flink
Issue Type: Improvement
Ingo Bürk created FLINK-22473:
-
Summary: Kinesis connector options are not listed by its factory
Key: FLINK-22473
URL: https://issues.apache.org/jira/browse/FLINK-22473
Project: Flink
Issue Type:
Leonard Xu created FLINK-22472:
--
Summary: The real partition data produced time is behind
meta(_SUCCESS) file produced
Key: FLINK-22472
URL: https://issues.apache.org/jira/browse/FLINK-22472
Project: Fli
Ingo Bürk created FLINK-22471:
-
Summary: Use formatted descriptions for connector options
Key: FLINK-22471
URL: https://issues.apache.org/jira/browse/FLINK-22471
Project: Flink
Issue Type: Improv
Dian Fu created FLINK-22470:
---
Summary: The root cause of the exception encountered during
compiling the job was not exposed to users in certain cases
Key: FLINK-22470
URL: https://issues.apache.org/jira/browse/FLINK-224
31 matches
Mail list logo