Hi all.
Expect to have such a mode of submission. Build the job directly in the
Environment, and then submit the job in yarn mode. Just like
RemoteStreamEnvironment, as long as you specify the parameters of the yarn
cluster (host, port) or yarn configuration directory and
Thomas Weise created FLINK-17496:
Summary: Performance regression with amazon-kinesis-producer
0.13.1 in Flink 1.10.x
Key: FLINK-17496
URL: https://issues.apache.org/jira/browse/FLINK-17496
Project:
XBaith edited a comment on pull request #333:
URL: https://github.com/apache/flink-web/pull/333#issuecomment-622439043
> Hey, David! Thanks a lot for doing the whole integration of the training —
it's a super valuable resource that indeed deserves more attention.
>
> What about
XBaith commented on pull request #333:
URL: https://github.com/apache/flink-web/pull/333#issuecomment-622439043
> Hey, David! Thanks a lot for doing the whole integration of the training —
it's a super valuable resource that indeed deserves more attention.
>
> What about linking
morsapaes commented on pull request #333:
URL: https://github.com/apache/flink-web/pull/333#issuecomment-622432180
Hey, David! Thanks a lot for doing the whole integration of the training —
it's a super valuable resource that indeed deserves more attention.
What about linking this
Hey,
(Switching to my personal email)
Correct me if I'm wrong, but I think Aljoscha is proposing keeping the
public API as is, and adding some new constructors/ custom deserialization
schemas as was done with Kafka. Here's what I was able to find on that
feature:
*
+1
I could see there's a thorough discussion and the solution looks good.
Thanks for driving this Yangze.
Best Regards,
Yu
On Fri, 1 May 2020 at 21:34, Till Rohrmann wrote:
> Thanks for updating the FLIP Yangze.
>
> +1 (binding)
>
> for the update.
>
> Cheers,
> Till
>
> On Thu, Apr 30, 2020
jinhai created FLINK-17495:
--
Summary: Add custom labels on PrometheusReporter like
PrometheusPushGatewayReporter's groupingKey
Key: FLINK-17495
URL: https://issues.apache.org/jira/browse/FLINK-17495
nobleyd created FLINK-17494:
---
Summary: Possible direct memory leak in cassandra sink
Key: FLINK-17494
URL: https://issues.apache.org/jira/browse/FLINK-17494
Project: Flink
Issue Type: Bug
Thanks for updating the FLIP Yangze.
+1 (binding)
for the update.
Cheers,
Till
On Thu, Apr 30, 2020 at 4:34 PM Yangze Guo wrote:
> Hi, there.
>
> The "FLIP-108: Add GPU support in Flink"[1] is now working in
> progress. However, we met problems regarding class loader and
> dependency. For
nobleyd created FLINK-17493:
---
Summary: Possible direct memory leak in cassandra sink
Key: FLINK-17493
URL: https://issues.apache.org/jira/browse/FLINK-17493
Project: Flink
Issue Type: Bug
nobleyd created FLINK-17492:
---
Summary: Possible direct memory leak in cassandra sink
Key: FLINK-17492
URL: https://issues.apache.org/jira/browse/FLINK-17492
Project: Flink
Issue Type: Bug
It seems that the link of the md file needs to be updated.
On Fri, May 1, 2020 at 7:10 AM David Anderson (Jira)
wrote:
> David Anderson created FLINK-17491:
> --
>
> Summary: Translate Training page on project website
> Key:
Hi everyone,
Please review and vote on the release candidate #2 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],
*
alpinegizmo commented on pull request #333:
URL: https://github.com/apache/flink-web/pull/333#issuecomment-622351679
I've created https://issues.apache.org/jira/browse/FLINK-17491 for the
Chinese translation.
This is an
alpinegizmo opened a new pull request #333:
URL: https://github.com/apache/flink-web/pull/333
Now that the documentation has a training section, it would be good to help
folks find it by promoting it from the project website.
This adds training.md and training.zh.md, and adds a
David Anderson created FLINK-17491:
--
Summary: Translate Training page on project website
Key: FLINK-17491
URL: https://issues.apache.org/jira/browse/FLINK-17491
Project: Flink
Issue Type:
David Anderson created FLINK-17490:
--
Summary: Add Training page to project website
Key: FLINK-17490
URL: https://issues.apache.org/jira/browse/FLINK-17490
Project: Flink
Issue Type:
Hello,
So the proposal is to keep the current RMQSource constructors / public api
as is and create new ones that gives more granular parsing ?
Regards,
Karim Mansour
On Thu, Apr 30, 2020 at 5:23 PM Austin Cawley-Edwards <
aus...@fintechstudios.com> wrote:
> Hey all + thanks Konstantin,
>
>
Timo Walther created FLINK-17489:
Summary: Support any kind of array in
StringUtils.arrayAwareToString()
Key: FLINK-17489
URL: https://issues.apache.org/jira/browse/FLINK-17489
Project: Flink
Hi Jark,
yes, in theory every connector can design options as they like. But for
user experience and good coding style we should be consistent in Flink
connectors and configuration. Because implementers of new connectors
will copy the design of existing ones.
Furthermore, I could image that
Khokhlov Pavel created FLINK-17488:
--
Summary: JdbcSink has to support setting auto-commit mode of DB
Key: FLINK-17488
URL: https://issues.apache.org/jira/browse/FLINK-17488
Project: Flink
22 matches
Mail list logo
