Feifan Wang created FLINK-24562:
---
Summary: YarnResourceManagerDriverTest should not use
ContainerStatusPBImpl.newInstance
Key: FLINK-24562
URL: https://issues.apache.org/jira/browse/FLINK-24562
Project:
Hi all,
We would like to start the vote for FLIP-174: Improve the WithParam
interface [1]. This FLIP was discussed in this thread [2].
The goal of this FLIP is to improve the experience of defining, saving and
loading parameters of stages (e.g. Transformer and Estimator) in the Flink
ML repo。
Th
Hi all,
We would like to start the vote for FLIP-175: Compose
Estimator/Model/AlgoOperator from DAG of Estimator/Model/AlgoOperator [1].
This FLIP was discussed in this thread [2].
With this FLIP, users can compose an Estimator from a DAG of
Estimator/Model/AlgoOperator by describing this DAG jus
Chesnay Schepler created FLINK-24561:
Summary: Build archetype jars in compile phase
Key: FLINK-24561
URL: https://issues.apache.org/jira/browse/FLINK-24561
Project: Flink
Issue Type: Tec
Chesnay Schepler created FLINK-24560:
Summary: flink-yarn-tests should copy examples after package phase
Key: FLINK-24560
URL: https://issues.apache.org/jira/browse/FLINK-24560
Project: Flink
Chesnay Schepler created FLINK-24559:
Summary: flink-rpc-akka-loader does not bundle flink-rpc-akka
Key: FLINK-24559
URL: https://issues.apache.org/jira/browse/FLINK-24559
Project: Flink
bai sui created FLINK-24558:
---
Summary: dataStream can not use multiple classloaders
Key: FLINK-24558
URL: https://issues.apache.org/jira/browse/FLINK-24558
Project: Flink
Issue Type: Improvement
weibo zhao created FLINK-24557:
--
Summary: Support Knn in FlinkML
Key: FLINK-24557
URL: https://issues.apache.org/jira/browse/FLINK-24557
Project: Flink
Issue Type: Bug
Components: Libr
Zhipeng Zhang created FLINK-24556:
-
Summary: Support Logistic Regression in FlinkML
Key: FLINK-24556
URL: https://issues.apache.org/jira/browse/FLINK-24556
Project: Flink
Issue Type: New Feat
Junfan Zhang created FLINK-24555:
Summary: Incorrectly put empty list to flink configuration
Key: FLINK-24555
URL: https://issues.apache.org/jira/browse/FLINK-24555
Project: Flink
Issue Type:
WangMinChao created FLINK-24554:
---
Summary: Support metadata columns for format-json
Key: FLINK-24554
URL: https://issues.apache.org/jira/browse/FLINK-24554
Project: Flink
Issue Type: New Featur
Agree. If the description contains more information than the return tag
comment. Part of content overlap is acceptable. Otherwise I think it
depends on the visibility and influence of the API. Agree again, it is not
a big issue for internal interfaces and classes. But for some core public
APIs that
Anton Kalashnikov created FLINK-24553:
-
Summary: Change buffer debloating default configuration values
Key: FLINK-24553
URL: https://issues.apache.org/jira/browse/FLINK-24553
Project: Flink
Dawid Wysakowicz created FLINK-24552:
Summary: Ineffective buffer debloat configuration in randomized
tests
Key: FLINK-24552
URL: https://issues.apache.org/jira/browse/FLINK-24552
Project: Flink
Anton Kalashnikov created FLINK-24551:
-
Summary: BUFFER_DEBLOAT_SAMPLES property is taken from the wrong
configuration
Key: FLINK-24551
URL: https://issues.apache.org/jira/browse/FLINK-24551
Proje
To me it sounds like a nice idea, to give the opportunity to users to combine
several
tasks together (even outside of flink) with TableResult.
On 2021/10/14 09:37:56, Francesco Guardiani wrote:
> I'm sorry, in the previous mail I was wrong and what I had in mind was the
> CompletableFuture.
>
Dawid Wysakowicz created FLINK-24550:
Summary: Can not access job information from a standby jobmanager
UI
Key: FLINK-24550
URL: https://issues.apache.org/jira/browse/FLINK-24550
Project: Flink
+1 for trying to clean this up, but I'm not entirely sure in which
direction. Usually I was fixing this towards option 1. I agree, in your
example option 2. looks much better, but usually the javadoc contains a bit
more information, not only copy/pasted @return text. For example:
/**
* Se
Dawid Wysakowicz created FLINK-24549:
Summary: FlinkKinesisConsumer does not work with generic types
disabled
Key: FLINK-24549
URL: https://issues.apache.org/jira/browse/FLINK-24549
Project: Flink
chenxy created FLINK-24548:
--
Summary: flink-connector-jdbc SQLException retry sleep have a
problem
Key: FLINK-24548
URL: https://issues.apache.org/jira/browse/FLINK-24548
Project: Flink
Issue Typ
Hi Flink developers,
It might be a good idea to avoid the redundant javadoc comment found in
some classes, e.g. org.apache.flink.core.fs.Path w.r.t. the @Return tag
comment on some methods.
To make the discussion clear, let's focus on a concrete example(there are
many more):
> /**
> * Returns t
jocean.shi created FLINK-24547:
--
Summary: A function named row_kind() can get row_kind
Key: FLINK-24547
URL: https://issues.apache.org/jira/browse/FLINK-24547
Project: Flink
Issue Type: New Feat
camilesing created FLINK-24546:
--
Summary: Acknowledged description miss on Monitoring Checkpointing
page
Key: FLINK-24546
URL: https://issues.apache.org/jira/browse/FLINK-24546
Project: Flink
I
linqichen created FLINK-24545:
-
Summary: job that read data from hive will finished even though i
set streaming mode
Key: FLINK-24545
URL: https://issues.apache.org/jira/browse/FLINK-24545
Project: Flink
I'm sorry, in the previous mail I was wrong and what I had in mind was the
CompletableFuture.
The use case I have in mind is a user that wants to fire say N batch jobs
and then, after all these are complete, fire a last job. If TableResult
extends CompletableFuture or has a method to convert to Co
Francesco Guardiani created FLINK-24544:
---
Summary: Failure when using Kafka connector in Table API with Avro
and Confluent schema registry
Key: FLINK-24544
URL: https://issues.apache.org/jira/browse/FLINK-2
Jun Qin created FLINK-24543:
---
Summary: Zookeeper connection issue causes inconsistent state in
Flink
Key: FLINK-24543
URL: https://issues.apache.org/jira/browse/FLINK-24543
Project: Flink
Issue Ty
zlzhang0122 created FLINK-24542:
---
Summary: Expose the freshness metrics for kafka connector
Key: FLINK-24542
URL: https://issues.apache.org/jira/browse/FLINK-24542
Project: Flink
Issue Type: Im
28 matches
Mail list logo