Hi all,
FYI, build issues for connectors related to architecture tests adding or
removing violations is under fixing and tracked here (1)
Of course, it is indeed not a blocker as connectors development is
decoupled from Flink development.
[1] https://issues.apache.org/jira/browse/FLINK-3256
Hi folks,
In the release managers' sync-up meeting today, we have discussed all
issues and came to a consensus that there are no blocking issues for 1.18
release. Since there were some new commits after rc1, I will create a rc2
now. Thanks again for your contributions.
Best regards,
Jing
On Mo
Hi Jing,
Thanks for looking into this
I checked it against opensearch connector [1] and it is green now
Also checked against hbase [2] which is now failing because of a different
issue
however anyway it was able to go further (before it failed at Download
Flink binary task) than when it was not p
Hi Folks,
Ververica has made the files publicly accessible. Could anyone check if any
connector build works again?
Best regards,
Jing
On Mon, Oct 9, 2023 at 9:07 AM Jing Ge wrote:
> Hi Sergey and devs,
>
> Thanks for bringing this to our attention. I am open to discuss that. I
> have the follo
Thanks Konstantin for opening the PR, appreciate it!
Best regards,
Jing
On Fri, Oct 6, 2023 at 2:03 PM Konstantin Knauf wrote:
> Hi everyone,
>
> I've just opened a PR for the release announcement [1] and I am looking
> forward to reviews and feedback.
>
> Cheers,
>
> Konstantin
>
> [1] https:/
Hi Sergey and devs,
Thanks for bringing this to our attention. I am open to discuss that. I
have the following thoughts:
1. Like I already mentioned in many other threads, build issues in
downstream repos should not block upstream release. I understand the
concern that developers want to have sta
Hi everyone,
I've just opened a PR for the release announcement [1] and I am looking
forward to reviews and feedback.
Cheers,
Konstantin
[1] https://github.com/apache/flink-web/pull/680
Am Fr., 6. Okt. 2023 um 11:03 Uhr schrieb Sergey Nuyanzin <
snuyan...@gmail.com>:
> sorry for not mentionin
sorry for not mentioning it in previous mail
based on the reason above I'm
-1 (non-binding)
also there is one more issue [1]
which blocks all the externalised connectors testing against the most
recent commits in
to corresponding branches
[1] https://issues.apache.org/jira/browse/FLINK-33175
On
Thanks for creating RC1
* Downloaded artifacts
* Built from sources
* Verified checksums and gpg signatures
* Verified versions in pom files
* Checked NOTICE, LICENSE files
The strange thing I faced is
CheckpointAfterAllTasksFinishedITCase.testRestoreAfterSomeTasksFinished
fails on AZP [1]
which
Thanks everyone for the efforts!
Checked the following:
- Downloaded artifacts
- Built Flink from source
- Verified checksums/signatures
- Verified NOTICE, LICENSE files
- Deployed dummy SELECT job via SQL gateway on standalone cluster, things
seemed fine according to the log files
+1 (non-bind
Thanks for the efforts!
+1 (non-binding)
* Verified versions in the poms
* Built from source
* Verified checksums and signatures
* Started basic workloads with kubernetes operator
* Verified NOTICE and LICENSE files
G
On Fri, Sep 29, 2023, 18:16 Matthias Pohl
wrote:
> Thanks for creating RC1.
Thanks for creating RC1. I did the following checks:
* Downloaded artifacts
* Built Flink from sources
* Verified SHA512 checksums GPG signatures
* Compared checkout with provided sources
* Verified pom file versions
* Went over NOTICE file/pom files changes without finding anything
suspicious
* D
Hi all,
Thanks to the team for this RC.
I did a quick check of this RC against user pipelines (1) coded with
DataSet (even if deprecated and soon removed), DataStream and SQL APIs
based on the small scope of this test, LGTM
+1 (non-binding)
[1] https://github.com/echauchot/tpcds-benchmark-f
13 matches
Mail list logo
