文报 created FLINK-26938:
--
Summary: HybridSource recovery from savepoint fails When flink
parallelism is greater than the number of Kafka partitions
Key: FLINK-26938
URL: https://issues.apache.org/jira/browse/FLINK-26938
Jingsong Lee created FLINK-26937:
Summary: Introduce Leveled compression for LSM
Key: FLINK-26937
URL: https://issues.apache.org/jira/browse/FLINK-26937
Project: Flink
Issue Type: Sub-task
Jingsong Lee created FLINK-26936:
Summary: Pushdown watermark to table store source
Key: FLINK-26936
URL: https://issues.apache.org/jira/browse/FLINK-26936
Project: Flink
Issue Type:
Jingsong Lee created FLINK-26935:
Summary: Sort records by sequence number when continuous reading
Key: FLINK-26935
URL: https://issues.apache.org/jira/browse/FLINK-26935
Project: Flink
+1 (binding)
Verified the following:
- shasums
- gpg signatures
- source does not contain any binaries
- built from source
- deployed via helm after adding the distribution webserver endpoint as
a helm registry
- all relevant files have license headers
On Wed, Mar 30, 2022
Márton Balassi created FLINK-26934:
--
Summary: Add reference to operator meetup talk to docs
Key: FLINK-26934
URL: https://issues.apache.org/jira/browse/FLINK-26934
Project: Flink
Issue
AHeise merged pull request #3:
URL: https://github.com/apache/flink-connector-elasticsearch/pull/3
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
Arian Rohani created FLINK-26933:
Summary: FlinkKinesisConsumer incorrectly determines shards as
newly discovered when tested against Kinesalite when consuming DynamoDB streams
Key: FLINK-26933
URL:
Sorry I replied on the wrong thread, i repost my answer here :)
As there was already a discussion in the doc, I'll just summarize my
opinions here on the proposed execution of this FLIP.
I think we should rather avoid exposing internal details, which I consider
Calcite to be part of, but rather
huweihua created FLINK-26932:
Summary: TaskManager hung in cleanupAllocationBaseDirs not exit.
Key: FLINK-26932
URL: https://issues.apache.org/jira/browse/FLINK-26932
Project: Flink
Issue Type:
Hi, I would like to explain a bit more about the current dissusion[1] for the
ways to decouple Hive connector with Flink Planner.
The background is to support Hive dialect, the Hive connector is dependent on
Flink Planner for the current implementation is generate RelNode and then
deliver the
Hi everyone,
Please review and vote on the release candidate #3 for the version 0.1.0 of
Apache Flink Kubernetes Operator,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
**Release Overview**
As an overview, the release consists of
MartijnVisser opened a new pull request #3:
URL: https://github.com/apache/flink-connector-elasticsearch/pull/3
Matching https://github.com/apache/flink/blob/master/.asf.yaml
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
MartijnVisser commented on pull request #2:
URL:
https://github.com/apache/flink-connector-elasticsearch/pull/2#issuecomment-1083167678
> > @JingGe Thanks for this! Should we also be able to run `mvn clean
install` ? I've tried that, but I'm getting getting some errors:
>
> looks
JingGe commented on pull request #2:
URL:
https://github.com/apache/flink-connector-elasticsearch/pull/2#issuecomment-1083166099
> @JingGe Thanks for this! Should we also be able to run `mvn clean install`
? I've tried that, but I'm getting getting some errors:
looks like a Java
MartijnVisser edited a comment on pull request #2:
URL:
https://github.com/apache/flink-connector-elasticsearch/pull/2#issuecomment-1083152212
@JingGe Thanks for this! Should we also be able to run `mvn clean install` ?
I've tried that, but I'm getting getting some errors:
```
MartijnVisser commented on pull request #2:
URL:
https://github.com/apache/flink-connector-elasticsearch/pull/2#issuecomment-1083152212
@JingGe Thanks for this! Should we also be able to run `mvn clean install` ?
I've tried that, but I'm getting getting some errors:
```
```
--
JingGe opened a new pull request #2:
URL: https://github.com/apache/flink-connector-elasticsearch/pull/2
## What is the purpose of the change
**Attention**: this PR is still under construction with the following tasks:
1. merge the change of #18634
2. remove all code and test
Yufan Sheng created FLINK-26931:
---
Summary: Pulsar sink's producer name should be unique
Key: FLINK-26931
URL: https://issues.apache.org/jira/browse/FLINK-26931
Project: Flink
Issue Type: Bug
[You are receiving this because you are subscribed to one or more user
or dev mailing list of an Apache Software Foundation project.]
ApacheCon draws participants at all levels to explore “Tomorrow’s
Technology Today” across 300+ Apache projects and their diverse
communities. ApacheCon showcases
Yang Wang created FLINK-26930:
-
Summary: Rethink last-state upgrade implementation in
flink-kubernetes-operator
Key: FLINK-26930
URL: https://issues.apache.org/jira/browse/FLINK-26930
Project: Flink
dalongliu created FLINK-26929:
-
Summary: Introduce adaptive hash join for batch sql optimization
Key: FLINK-26929
URL: https://issues.apache.org/jira/browse/FLINK-26929
Project: Flink
Issue
Qingsheng Ren created FLINK-26928:
-
Summary: Remove unnecessary Docker network creation in Kafka
connector tests
Key: FLINK-26928
URL: https://issues.apache.org/jira/browse/FLINK-26928
Project: Flink
Qingsheng Ren created FLINK-26927:
-
Summary: Support restarting JobManager in FlinkContainers
Key: FLINK-26927
URL: https://issues.apache.org/jira/browse/FLINK-26927
Project: Flink
Issue
Thanks Marton,
I vote for consistency and `flink-kubernetes-operator` as well.
`flink-operator` have been used widely in docker hub and other k8s operator
implementations, which may confuse users.
Best,
Biao
Gyula Fóra 于2022年3月30日周三 16:26写道：
> Thanks Marton!
> I think we should aim for
Gyula Fora created FLINK-26926:
--
Summary: Allow users to force upgrade even if savepoint is in
progress
Key: FLINK-26926
URL: https://issues.apache.org/jira/browse/FLINK-26926
Project: Flink
Thanks Marton!
I think we should aim for consistency and easy discoverability. Since we
use the name `flink-kubernetes-operator` for the project and everywhere on
the website to refer to it, I suggest adopting it as the name also.
This should be a very simple change that we can easily do before
Hi devs,
Some SQL Table properties contain sensitive data, like passwords that we do not
want to expose in the VVP ui to other users. Also, having them clear text in a
SQL statement is not secure. For example,
CREATE TABLE Orders (
`user` BIGINT,
product STRING,
order_time
Spongebob created FLINK-26925:
-
Summary: loss scale in union situation
Key: FLINK-26925
URL: https://issues.apache.org/jira/browse/FLINK-26925
Project: Flink
Issue Type: Bug
Hi team,
I would like to ask for your input in naming the operator docker image and
helm chart. [1]
For the sake of brevity when we started the Kubernetes Operator work we
named the docker image and the helm chart simply flink-operator, while the
git repository is named
Márton Balassi created FLINK-26924:
--
Summary: Decide on operator docker image name
Key: FLINK-26924
URL: https://issues.apache.org/jira/browse/FLINK-26924
Project: Flink
Issue Type:
Yun Gao created FLINK-26923:
---
Summary: SavepointITCase.testStopWithSavepointFailsOverToSavepoint
failed on azure
Key: FLINK-26923
URL: https://issues.apache.org/jira/browse/FLINK-26923
Project: Flink
Hi Devs,
I am cancelling the current vote as we have promoted
https://issues.apache.org/jira/browse/FLINK-26916 as a blocker issue.
Yang has found a fix that we can reasonably do in a short time frame, so we
will work on that today before creating the next RC (hopefully later today)
Thank you!
Yun Gao created FLINK-26922:
---
Summary:
KafkaSinkITCase.testRecoveryWithExactlyOnceGuaranteeAndConcurrentCheckpoints
failed on azure
Key: FLINK-26922
URL: https://issues.apache.org/jira/browse/FLINK-26922
Yun Gao created FLINK-26921:
---
Summary: KafkaSinkE2ECase.testStartFromSavepoint failed on azure
Key: FLINK-26921
URL: https://issues.apache.org/jira/browse/FLINK-26921
Project: Flink
Issue Type:
Dian Fu created FLINK-26920:
---
Summary: It reported "The configured managed memory fraction for
Python worker process must be within (0, 1], was: %s."
Key: FLINK-26920
URL:
36 matches
Mail list logo
