Thank you all for the input, let’s consider this a blocker.
As soon as we have the NOTICE fix , I will prepare the new RC.
Gyula
On Tue, 29 Mar 2022 at 06:51, Yang Wang wrote:
> Given that *flink-kubernetes-shaded* already contains a NOTICE file, and
> *flink-kubernetes-webhook* does not
Yang Wang created FLINK-26903:
-
Summary: Add correct NOTICE file to flink-kubernetes-operator
Key: FLINK-26903
URL: https://issues.apache.org/jira/browse/FLINK-26903
Project: Flink
Issue Type:
Given that *flink-kubernetes-shaded* already contains a NOTICE file, and
*flink-kubernetes-webhook* does not bundle any dependencies.
IIUC, what we should do now is to add a correct NOTICE file only for the
*flink-kubernetes-operator* module.
If I do not miss anything, this would not be very
Jingsong Lee created FLINK-26902:
Summary: Introduce benchmark document for table store
Key: FLINK-26902
URL: https://issues.apache.org/jira/browse/FLINK-26902
Project: Flink
Issue Type:
Jingsong Lee created FLINK-26901:
Summary: Introduce config options document for table store
Key: FLINK-26901
URL: https://issues.apache.org/jira/browse/FLINK-26901
Project: Flink
Issue
Jingsong Lee created FLINK-26900:
Summary: Introduce Best Practices document for table store
Key: FLINK-26900
URL: https://issues.apache.org/jira/browse/FLINK-26900
Project: Flink
Issue
Jingsong Lee created FLINK-26899:
Summary: Introduce query table document for table store
Key: FLINK-26899
URL: https://issues.apache.org/jira/browse/FLINK-26899
Project: Flink
Issue Type:
Jingsong Lee created FLINK-26898:
Summary: Introduce creating table document for table store
Key: FLINK-26898
URL: https://issues.apache.org/jira/browse/FLINK-26898
Project: Flink
Issue
I believe if we as the PMC distribute a docker image (which is optional,
"convenience"), then that image has to follow the rules for binary packages
[1]. (And I would assume that applies regardless where we host the images.)
Now to say that we only publish sources kind of side steps that problem.
liuzhuo created FLINK-26897:
---
Summary: Provide an additional way to add dependency files to k8s
Key: FLINK-26897
URL: https://issues.apache.org/jira/browse/FLINK-26897
Project: Flink
Issue Type:
Koala Lam created FLINK-26896:
-
Summary: Logging - Support yaml/xml/json format in Log4j2
Key: FLINK-26896
URL: https://issues.apache.org/jira/browse/FLINK-26896
Project: Flink
Issue Type:
Dear Community,
We are fairly on track with stabilising the 1.15 release, that’s why Yun Gao
and me think we don’t need the sync anymore.
So we skip it for now, starting from tomorrow. If the situation might change.
We will let you know.
Best,
Joe
Gyula Fora created FLINK-26895:
--
Summary: Improve cancelWithSavepoint timeout error message
Key: FLINK-26895
URL: https://issues.apache.org/jira/browse/FLINK-26895
Project: Flink
Issue Type:
Gyula Fora created FLINK-26894:
--
Summary: Support custom validator implementations
Key: FLINK-26894
URL: https://issues.apache.org/jira/browse/FLINK-26894
Project: Flink
Issue Type: New Feature
Gyula Fora created FLINK-26893:
--
Summary: Validate checkpoint config with last-state upgrade mode
Key: FLINK-26893
URL: https://issues.apache.org/jira/browse/FLINK-26893
Project: Flink
Issue
Gyula Fora created FLINK-26892:
--
Summary: Observe current status before validating CR changes
Key: FLINK-26892
URL: https://issues.apache.org/jira/browse/FLINK-26892
Project: Flink
Issue Type:
Gyula Fora created FLINK-26891:
--
Summary: Emit events for important Deployment / Job changes
Key: FLINK-26891
URL: https://issues.apache.org/jira/browse/FLINK-26891
Project: Flink
Issue Type:
I see your point and the value for having such a notice added.
I think there are 2 completely distinct questions at play here:
a) Is there a legal requirement for a NOTICE file for the docker image?
b) If not, should we block the release on this and add it immediately?
For a)
I think from a
One difference to Flink is that the distribution bundled in the docker
image still contains the NOTICE covering the contents of it.
It may admittedly not be the most discoverable place, but a reasonable
one I think.
Docker as a whole is very weird when it comes to licensing.
Think of all the
Thanks for the input!
I am not an expert on this topic and have been contemplating this myself
also.
We are basically trying to follow the precedent set by Flink and Statefun
projects where the docker builds that we use to publish images to
dockerhub do not declare any notices.
We will not use
I don't think having users build the fat-jar & docker image absolves us
of all responsibility w.r.t. the licensing of used products.
At the very least we need to inform users what licenses the fat-jar &
docker image fall under such that they can make an informed decision as
to whether they
Danny Cranmer created FLINK-26890:
-
Summary: [Kinesis][Consumer] DynamoDB consumer error consuming
partitions close to retention
Key: FLINK-26890
URL: https://issues.apache.org/jira/browse/FLINK-26890
Hi Chesnay,
Let me try to explain the "strange stuff"
flink-kubernetes-shaded relocates some classes found in flink-kubernetes in
order to not conflict with some of the operator dependencies.
This is necessary as flink-kubernetes packages almost everything in the
fat-jar as-is without
There's some strange stuff in here.
What exactly is the purpose of flink-kubernetes-shaded? You're just
re-packaging flink-kubernetes without making any changes.
The uploaded flink-kubernetes-operator jar isn't bundling any
dependencies. Why is the fat jar not uploaded? Is it used anywhere
Aitozi created FLINK-26889:
--
Summary: Eliminate the duplicated construct for
FlinkOperatorConfiguration in test
Key: FLINK-26889
URL: https://issues.apache.org/jira/browse/FLINK-26889
Project: Flink
Chesnay Schepler created FLINK-26888:
Summary: Add e2e tests for network partitions
Key: FLINK-26888
URL: https://issues.apache.org/jira/browse/FLINK-26888
Project: Flink
Issue Type:
Chesnay Schepler created FLINK-26887:
Summary: Drop Jepsen tests
Key: FLINK-26887
URL: https://issues.apache.org/jira/browse/FLINK-26887
Project: Flink
Issue Type: Technical Debt
Hi everyone,
Please review and vote on the release candidate #1 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
Chesnay Schepler created FLINK-26886:
Summary: Document reporter behavior w.r.t. scopes & push/pull
Key: FLINK-26886
URL: https://issues.apache.org/jira/browse/FLINK-26886
Project: Flink
Chesnay Schepler created FLINK-26885:
Summary: Cleanup MetricRegistryImplTest
Key: FLINK-26885
URL: https://issues.apache.org/jira/browse/FLINK-26885
Project: Flink
Issue Type: Technical
Jing Ge created FLINK-26884:
---
Summary: Move Elasticsearch connector to external connector
repository
Key: FLINK-26884
URL: https://issues.apache.org/jira/browse/FLINK-26884
Project: Flink
Issue
zl created FLINK-26883:
--
Summary: Bump dependency-check-maven to 2.10.1
Key: FLINK-26883
URL: https://issues.apache.org/jira/browse/FLINK-26883
Project: Flink
Issue Type: Improvement
Thanks Martijn, a few of these administrative bits are still work in
progress :)
Gyula
On Mon, 28 Mar 2022 at 11:31, Martijn Visser
wrote:
> Hi Gyula,
>
> The documentation on https://flink.apache.org/ currently shows 'Flink
> Kubernetes Operator 1.0 (Latest stable release)'.
>
> Best regards,
Hi Gyula,
The documentation on https://flink.apache.org/ currently shows 'Flink
Kubernetes Operator 1.0 (Latest stable release)'.
Best regards,
Martijn
On Mon, 28 Mar 2022 at 10:54, Gyula Fóra wrote:
> Hi Flink devs!
>
> The release-0.1 branch has been forked from main and version numbers
Sorry for this email, seems there's some format issue in my email client. Just
ignore it for it's a duplicate of [DISCUSS] FLIP-216 Decouple Hive connector
with Flink planner [1]
[1] https://lists.apache.org/thread/6xg33nxrnow5zy7xwqk5nwp00h9gcsbc
Best regards,
Hi Flink devs!
The release-0.1 branch has been forked from main and version numbers have
been upgraded accordingly.
https://github.com/apache/flink-kubernetes-operator/tree/release-0.1
The version on the main branch remains 1.0-SNAPSHOT for now.
>From now on, for PRs that should be presented
Yun Tang created FLINK-26882:
Summary: Unaligned checkpoint with 0s timeout would fail
RescaleCheckpointManuallyITCase
Key: FLINK-26882
URL: https://issues.apache.org/jira/browse/FLINK-26882
Project:
Hi,everyone
IwouldliketoopenadiscussionaboutdecouplingHiveconnectorwithFlinktableplanner.
Yang Wang created FLINK-26881:
-
Summary: Stop with savepoint should pick up the targetDirectory
from Flink configuration
Key: FLINK-26881
URL: https://issues.apache.org/jira/browse/FLINK-26881
Project:
Yun Gao created FLINK-26880:
---
Summary:
PyFlinkStreamUserDefinedFunctionTests.test_udf_in_join_condition failed on azure
Key: FLINK-26880
URL: https://issues.apache.org/jira/browse/FLINK-26880
Project:
Jane Chan created FLINK-26879:
-
Summary: LogStartupMode.LATEST does not work
Key: FLINK-26879
URL: https://issues.apache.org/jira/browse/FLINK-26879
Project: Flink
Issue Type: Bug
41 matches
Mail list logo
