eady,
> while mutating the values at runtime is actually an undefined behavior.
>
> Thanks,
> Zhu
>
> Tzu-Li (Gordon) Tai 于2023年4月18日周二 01:02写道：
> >
> > Hi,
> >
> > Sorry for chiming in late.
> >
> > I'm not so sure that exposing ExecutionConfig
> I have already modified FLIP-288 to provide a
newDiscoveryOffsetsInitializer in the KafkaSourceBuilder and
KafkaSourceEnumerator. Users can use
KafkaSourceBuilder#setNewDiscoveryOffsets to change the strategy for new
partitions.
Thanks for addressing my comment Hongshun.
> Considering these rea
+1
On Thu, Apr 20, 2023 at 11:52 PM Hongshun Wang
wrote:
> Dear Flink Developers,
>
>
> Thank you for providing feedback on FLIP-288: Enable Dynamic Partition
> Discovery by Default in Kafka Source[1] on the discussion thread[2].
>
> The goal of the FLIP is to enable partition discovery by defau
The Apache Flink community is very happy to announce the release of Apache
Flink Kafka Connectors 3.0.0. This release is compatible with the Apache
Flink 1.17.x release series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accur
Hi,
> I think we can get the serializer directly in InitContextImpl through
`getOperatorConfig().getTypeSerializerIn(0,
getUserCodeClassloader()).duplicate()`.
This should work, yes.
+1 to the updated FLIP so far. Thank you, Joao, for being on top of this!
Thanks,
Gordon
On Tue, May 30, 2023 a
Hi Mason,
Thanks for updating the FLIP. In principle, I believe this would be a
useful addition. Some comments so far:
1. In this sequence diagram [1], why is there a need for a
GetMetadataUpdateEvent from the MultiClusterSourceReader going to the
MultiClusterSourceEnumerator? Shouldn't the enume
in addition to what you mentioned, to use this in single cluster
> mode (see *[1] *above). DynamicKafkaSource may be confusing because it is
> really similar to the KafkaDynamicSource/Sink (table connectors).
>
> Best,
> Mason
>
> On Wed, Jun 7, 2023 at 10:40 AM Tzu-Li (Gordon) Tai
h, as described in
> > the FLIP, lossless consumer migration only works with a strategy that
> > involves intermittent parallel consumption of old and new clusters to
> drain
> > and switch.)
> >
> > I think the "Table" in the name of those SQL connectors should
+1 (binding)
+1 for either DynamicKafkaSource or DiscoveringKafkaSource
Cheers,
Gordon
On Thu, Jun 15, 2023, 10:56 Mason Chen wrote:
> Hi all,
>
> Thank you to everyone for the feedback on FLIP-246 [1]. Based on the
> discussion thread [2], we have come to a consensus on the design and are
> r
+1 (binding)
On Fri, Jun 16, 2023, 09:53 Jing Ge wrote:
> +1(binding)
>
> Best Regards,
> Jing
>
> On Fri, Jun 16, 2023 at 10:10 AM Lijie Wang
> wrote:
>
> > +1 (binding)
> >
> > Thanks for driving it, Joao.
> >
> > Best,
> > Lijie
> >
> > Joao Boto 于2023年6月16日周五 15:53写道：
> >
> > > Hi all,
> >
> Perhaps he could weigh in on whether the combination of automated tests
plus those smoke tests should be sufficient for testing with new Flink
versions
What we usually did at the bare minimum for new StateFun releases was the
following:
1. Build tests (including the smoke tests in the e2e mo
+1
On Wed, Jul 20, 2022 at 6:13 AM Danny Cranmer
wrote:
> Hi there,
>
> After the discussion in [1], I’d like to open a voting thread for FLIP-252
> [2], which proposes the addition of an Amazon DynamoDB sink based on the
> Async Sink [3].
>
> The vote will be open until July 23rd earliest (72h)
Hi Danny,
Thanks for starting a RC for this.
>From the looks of the staged POMs for 1.1.0-1.18, the flink versions for
Flink dependencies still point to 1.17.1.
My understanding is that this is fine, as those provided scope
dependencies (e.g. flink-streaming-java) will have their versions
overwr
Hi everyone,
Please review and vote on release candidate #1 for version 3.0.2 of the
Apache Flink Kafka Connector, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
Compared to the previous hotfix release, this release only additionally
.15.2:compile
[INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.17.1:runtime
[INFO] +- org.apache.logging.log4j:log4j-api:jar:2.17.1:runtime
[INFO] \- org.apache.logging.log4j:log4j-core:jar:2.17.1:runtime
```
On Fri, Nov 24, 2023 at 9:19 AM Tzu-Li (Gordon) Tai
wrote:
> Hi everyone,
>
>
ies
> > > > - build source maven 3.8.6 and jdk11
> > > > - verified web PR
> > > >
> > > > Best regards,
> > > > Jing
> > > >
> > > > On Sat, Nov 25, 2023 at 6:44 AM Rui Fan <1996fan...@gmail.com>
> wr
The Apache Flink community is very happy to announce the release of Apache
Flink Kafka Connectors 3.0.2. This release is compatible with the Apache
Flink 1.17.x and 1.18.x release series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available
+1 (binding) looks good to me overall
thank you for revising the FLIP and continuing to drive the decision, Peter!
On Wed, Dec 27, 2023 at 7:16 AM Martijn Visser
wrote:
> Hi Peter,
>
> It would be good if Gordon can take a look, but overall this looks good to
> me +1
>
> Best regards,
>
> Marti
Hi Filip,
Thanks for bringing this up.
The hard truth is that committers who were previously active on the
StateFun subproject, including myself, all currently have other focuses.
Indeed, we may need to discuss with the community on how to proceed if
there seems to be no continued committer cover
+1
On Fri, Oct 28, 2022 at 10:21 AM Konstantin Knauf wrote:
> +1 (binding)
>
> Am Fr., 28. Okt. 2022 um 16:58 Uhr schrieb Piotr Nowojski <
> pnowoj...@apache.org>:
>
> > Hi,
> >
> > As discussed on the dev mailing list [0] I would like to start a vote to
> > drop support of older savepoint forma
+1. Thanks Hangxiang, the proposed plan looks good!
On Sun, Oct 30, 2022 at 3:38 AM Yu Li wrote:
> +1 (binding)
>
> Thanks Hangxiang for driving this and thanks all for the thorough
> discussion.
>
> Best Regards,
> Yu
>
>
> On Fri, 28 Oct 2022 at 16:01, Dawid Wysakowicz
> wrote:
>
> > +1,
> >
> >>>>>> I last checked a few years back didn't have access to keyed state)
> >>>>>>
> >>>>>>
> >>>>>> P.S. Please note that there is already a pull request that has
> >>>
24 hours before cutting the release branch for 3.3.x, unless
anyone raises any objections before that.
Thanks,
Gordon
On Tue, Nov 1, 2022 at 10:09 AM Galen Warren
wrote:
> Thanks Gordon and Filip, I appreciate your help on this one.
>
> On Tue, Nov 1, 2022 at 1:07 PM Tzu-Li (Gordon) Tai
&g
FYI, release-3.3 branch has been cut and is ready for the release process
for StateFun 3.3.0:
https://github.com/apache/flink-statefun/tree/release-3.3
On Tue, Nov 1, 2022 at 10:21 AM Tzu-Li (Gordon) Tai
wrote:
> Btw, I'll assume that we're using this thread to gather consens
ainly
be better to get the release out ASAP.
[1]
https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Stateful+Functions+Release
On Fri, Nov 4, 2022 at 5:54 AM Galen Warren wrote:
> Thanks Gordon.
>
> What is the next step here?
>
> On Thu, Nov 3, 2022 at 1:45 P
Hi,
You are now assigned to the JIRA. You can now also assign tickets to yourself
in the future.
Cheers,
Gordon
On 11 September 2018 at 10:02:06 AM, Xinyu Zhang (wsz...@gmail.com) wrote:
Hi
I have finished some works for issue FLINK-10002(
https://issues.apache.org/jira/browse/FLINK-10002)
+1 (binding)
- Verified checksums / signatures
- Checked announcement PR in flink-web
- Built Flink from sources, test + build passes (Hadoop-free, Scala 2.11)
- Ran Elasticsearch 6 sink, using quickstart POM.
- Ran end-to-end tests locally, passes
On Thu, Sep 20, 2018 at 4:31 PM Till Rohrmann w
+1 (binding)
- Verified checksums / signatures
- Checked announcement PR in flink-web
- No new / changed dependencies
- Built from source (Hadoop-free, Scala 2.11)
- Run end-to-end tests locally, passes
On Thu, Sep 20, 2018 at 5:03 AM Fabian Hueske wrote:
> +1 binding
>
> * I checked the diffs
+1
- Checked signature and hashes
- Built locally with current master branch
Couldn't find anything blocking either.
Cheers,
Gordon
On Thu, Oct 11, 2018 at 4:33 PM Timo Walther wrote:
> +1
>
> - I built locally and checked the JAR files for suspicious things.
> - I went throught the change di
Hi,
I’m forwarding this question to Stefan (cc’ed).
He would most likely be able to answer your question, as he has done
substantial work in the RocksDB state backends.
Cheers,
Gordon
On 24 October 2018 at 8:47:24 PM, chandan prakash (chandanbaran...@gmail.com)
wrote:
Hi,
I am new to Flink.
+1
- Verified signature and hashes
- Built locally, with Scala 2.11, Hadoop free. Build passes without errors.
- Ran e2e tests locally overnight in a loop, no attempts were failing
- No missing artifacts in the release staging area.
I also agree that the OS-incompatibility in ES shouldn’t be bloc
+1
- Built locally, with Scala 2.11, Hadoop free. Build passes without errors
(failed on HBaseConnectorITCase but passed after restarting the build from the
Hbase connector).
- Verified signature and hashes
- Ran e2e tests locally overnight in a loop, no attempts were failing
- No missing artifa
Hi Thomas,
I think Stefan Richter is also working on the Kinesis end-to-end test, and
seems to be planning to implement it against a real Kinesis service instead
of Kinesalite.
Perhaps efforts should be synced here.
Cheers,
Gordon
On Thu, Nov 8, 2018 at 1:38 PM Thomas Weise wrote:
> Hi,
>
> I
+1
Functional checks:
- Built Flink from source (`mvn clean verify`) locally, with success
- Run all nightly end-to-end tests locally for 5 times in a loop, no
attempts failed (Hadoop 2.8.3, Scala 2.12)
- Tested Java quickstart + modified to include Kafka 1.0 connector and
Elasticsearch 6.0 conne
Hi,
You now have contributor permissions and can assign JIRAs you would like to
work on to yourself.
Welcome to the community!
Cheers,
Gordon
On Fri, Dec 7, 2018, 11:17 AM sf lee Hi there,
> Could anyone kindly give me the contributor permission?
> My JIRA id is xleesf.
>
> Thanks,
>
> xleesf
Hi Flink community,
I would like to ask what you think about releasing 1.6.3.
There's a few critical fixes in the 1.6 branch that users would benefit
from with another bugfix release for the series.
Some are already mentioned by Till in the recent 1.5.6 release discussion
thread, and their fixes
Hi,
Besides the information that Chesnay requested, could you also provide a stack
trace of the exception that caused the job to terminate in the first place?
The Elasticsearch sink does indeed close the internally used Elasticsearch
client, which should in turn properly release all resources [
ill
> > >
> > > On Wed, Dec 12, 2018 at 12:58 PM vino yang
> > wrote:
> > >
> > > > Hi Gordon,
> > > >
> > > > +1 to release Flink 1.6.3.
> > > >
> > > > Best,
> > > > Vino
> > > >
> > &
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.6.3, 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],
missing any jars
> >> - tag exists
> >> - release notes classification/names seem appropriate
> >> - maven artifacts not missing any jars
> >>
> >> On 18.12.2018 11:15, Tzu-Li (Gordon) Tai wrote:
> >>> Hi everyone,
> >>&g
I'm happy to announce that we have unanimously approved this release.
There are 5 approving votes, all of which are binding:
* Chesnay Schepler (binding)
* Aljoscha Krettek (binding)
* Timo Walther (binding)
* Till Rohrmann (binding)
* Tzu-Li Tai (binding)
There are no disapproving votes.
Hi,
The Apache Flink community is very happy to announce the release of
Apache Flink 1.6.3, which is the third bugfix release for the Apache
Flink 1.6 series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data
str
Makes sense if we haven't been using them.
+1 to drop.
On Thu, Jan 3, 2019 at 2:45 PM Aljoscha Krettek wrote:
> Sounds good.
>
> > On 3. Jan 2019, at 14:27, Chesnay Schepler wrote:
> >
> > Since neither of these repositories are in use (flink-libraries is
> empty, and incubator-flink is 3+ year
Hi Robert,
Thanks a lot for starting this discussion!
+1 to a user-zh@flink.a.o mailing list (you mentioned -zh in the title, but
-cn in the opening email content.
I think -zh would be better as we are establishing the tool for general
Chinese-speaking users).
All dev@ discussions / JIRAs should
Hi,
Great seeing efforts in pushing this forward, Jark!
A bit late in the party here, but I just want to also point out that:
- +1 to https://flink.apache.org/zh/ as the website address
- Add to the contribution checklist in PRs that both English / Chinese docs
have been updated accordingly.
I
Hi Flink devs,
What do you think about releasing Flink 1.7.2 soon?
We already have some critical fixes in the release-1.7 branch:
- FLINK-11207: security vulnerability with currently used Apache
commons-compress version
- FLINK-11419: restore issue with StreamingFileSink
- FLINK-11436: restore is
> wrote:
> >
> > > +1 for starting Flink 1.7.2 release next week.
> > >
> > > Cheers,
> > > Jincheng
> > >
> > > Tzu-Li (Gordon) Tai 于2019年2月5日周二 下午11:32写道：
> > >
> > > > Hi Flink devs,
> > > >
> > > > Wha
st to
> not block 1.7.2 on this issue.
>
> Cheers,
> Till
>
> On Mon, Feb 11, 2019 at 2:32 AM Tzu-Li (Gordon) Tai
> wrote:
>
>> Hi,
>>
>> Thanks for the replies.
>>
>> @Shuyi, I prefer not to block release of 1.7.2 with FLINK-10868.
>> It doe
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.7.2,
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],
*
>
> > >>
> > >> On Mon, Feb 4, 2019 at 1:23 PM Jark Wu wrote:
> > >>
> > >>> Hi all,
> > >>>
> > >>> I have drafted the proposal:
> > >>>
> > >>>
> > >>
> >
> https://docs.goo
to say.
My intention is that at least the English documentation should always be
updated. If the contributor is non-Chinese speaking, then a JIRA should be
opened to keep track of syncing the Chinese docs.
Cheers,
Gordon
> Btw, I like the "zh-doc" label!
>
> Regards,
> Jark
+1 (binding)
- Checked signatures and hashes
- built from source archive with success
On Sun, Feb 10, 2019 at 4:51 PM Chesnay Schepler wrote:
> +1 (binding)
>
> The release prefix is now added to the tag to be more consistent with
> the main Flink releases.
>
> On 08.02.2019 15:52, jincheng sun
Thanks for driving the release for 1.6.4 Jincheng!
+1
On Tue, Feb 12, 2019 at 5:32 PM Hequn Cheng wrote:
> Hi Jincheng,
>
> +1
>
> Thank you for the discuss and writing a very nice google doc.
> Looking forward to the 1.6.4 release. :-)
>
> Best, Hequn
>
>
> On Tue, Feb 12, 2019 at 5:23 PM Shao
Hi,
Welcome! I assigned you contributor permissions on JIRA.
Cheers,
Gordon
On Wed, Feb 13, 2019 at 10:59 AM huadong sun wrote:
> Hello，
>
> Did anyone see me？😭
>
> > 在 2019年2月12日，下午6:33，孙华栋 写道：
> >
> > Hi Guys,
> >
> > I want to contribute to Apache Flink,
> > Would you please give me the pe
Hi Robert,
I'll be willing to help with moderating the user-zh@ list.
Cheers,
Gordon
On Wed, Feb 13, 2019 at 5:05 PM Robert Metzger wrote:
> Hey all,
>
> I'm now getting more and more MODERATE emails from the mailing list service
> for the user-zh@ list from people trying to subscribe.
> I wou
Hi,
Partition offsets stored in state will always be respected when the
consumer is restored from checkpoints / savepoints.
AFAIK, this seems to have been the behaviour for quite some time now (since
FlinkKafkaConsumer08).
I think in the past there were some discussion to at least allow some way
Hi!
Welcome to the community. I gave you contributor permissions in JIRA.
Cheers,
Gordon
On Fri, Feb 15, 2019 at 11:19 AM 炯炯 wrote:
> Hi, my name is James Guo. I am a Apache Flink lovers and wanna become
> a Flink contributor.
>
> My JIRA ID is James Guo. Hope to be allowed !
Hi,
Welcome to the community, Hui! I gave you contributor permissions in JIRA.
Cheers,
Gordon
On Fri, Feb 15, 2019 at 10:39 AM 赵慧 wrote:
> Hi Guys,
>
> I want to contribute to Apache Flink.
> Would you please give me the permission as a contributor?
> My JIRA ID is Cynthia Zhao.
+1
- checked signatures and hashes
- no missing artifacts in release staging area
- built from source, without Hadoop and using Scala 2.12
- ran end-to-end tests locally and succeeded
- manually tested that a job using Avro as state type can be restored from
1.6.3 with the 1.7.2 RC
- a user previo
)
There are no disapproving votes.
Thanks everyone!
@Chesnay thanks for checking the release notes. I’ll make sure the
announcement post is updated with the new notes.
On Fri, Feb 15, 2019 at 10:05 PM Tzu-Li (Gordon) Tai
wrote:
> +1
>
> - checked signatures and hashes
> - no missi
t;> I’m just wondering if there are real world use cases for maintaining
> > this
> > >> default behavior. It’s a bit counter intuitive and sometimes results
> in
> > >> serious production issues. ( We had a similar issue when changing the
> > topic
>
d problems?
> > Or an example where someone might reasonably expect the current behaviour
> > instead of the newly suggested one.
> >
> > If we have such cases I would agree lets keep it as is. If we cant come
> up
> > with anything reasonable I vote for changing
Hi,
The Apache Flink community is very happy to announce the release of
Apache Flink 1.7.2, which is the second bugfix release for the Apache
Flink 1.7 series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data
streami
Hi Robert,
Regarding FLINK-10776 - Update migration tests for Flink 1.7:
There's still one last test class that needs to be migrated (progress
reflected in the list of subtasks of FLINK-10776), and we definitely should
still fix that before releasing 1.8.0 to ensure backwards compatibility of
save
Hi,
Thanks for reporting this.
I'm not entirely sure what happened with the build here - the master branch
is building without the error at the moment.
Also, your latest Travis run on the PR is passing:
https://travis-ci.org/apache/flink/builds/494952794
So, I would say, considering your PR it is
Hi Feng,
Regarding your particular contribution:
I think you did a good job in gathering consensus on how the fix should be
addressed.
The PR's changes also matches the original discussions, with good test
coverage and quality all in all.
The only thing lacking was more attention from reviewers t
Hi Fokko,
I've looked at FLINK-11911 (Make KafkaTopicPartition a POJO), and left a
comment in the PR.
Main gist is that this change would break state compatibility for previous
versions of the FlinkKafkaConsumers, since changing that behind the scenes
Flink would use different serializers for the
@Yu
Thanks for reporting that Yu, great that this was noticed.
The serializerAvro case seems to only be testing on-wire serialization.
I checked the changes to the `AvroSerializer`, and it seems like
FLINK-11436 [1] with commit 479ebd59 was the only change that may have
affected that.
That commit
> > love). Let me mark this as one of my backlog and will open a JIRA when
> > prepared.
> >
> > Anyway good to know it's not a regression, and thanks for the efforts
> spent
> > on checking it over! @Gordon @Chesnay
> >
> > Best Regards,
> > Yu
Hi Izual,
Thanks for reporting this! I'm also forwarding this to the user mailing
list, as that is the more suitable place for this question.
I think the usability of the State Processor API in Scala is indeed
something that hasn’t been looked at closely yet.
On Tue, Jan 21, 2020 at 8:12 AM izua
Congratulations :)
On Thu, Jan 23, 2020, 5:07 PM Yadong Xie wrote:
> Well deserved!
>
> Yangze Guo 于2020年1月23日周四 下午5:06写道：
>
> > Congratulations!
> >
> > Best,
> > Yangze Guo
> >
> >
> > On Thu, Jan 23, 2020 at 4:59 PM Stephan Ewen wrote:
> > >
> > > Hi all!
> > >
> > > We are announcing that
+1 (binding)
- checked signatures and hashes
- built from source (mvn clean package, Scala 2.12)
- ran e2e tests locally
- checked new dependencies for licenses, no new ones were included since
1.9.1
- ran Kafka example with local cluster
- quickstart worked without errors, logs looked good
- Webs
+1 (binding)
Cheers,
Gordon
On Fri, Jan 31, 2020 at 2:16 PM Jingsong Li wrote:
> +1 (non-binding)
>
> Official docker support really looks good to me.
>
> Best,
> Jingsong Lee
>
> On Fri, Jan 31, 2020 at 12:55 AM aihua li wrote:
>
> > +1 (non-binding)
> >
> > > 2020年1月30日 下午7:36，Igal Shilman
Hi devs,
I’d like to briefly provide an update / overview on what has been going on
in the Flink Stateful Functions project since it was moved to Apache Flink
[1].
One other main purpose of this is to figure out the next steps for the
project, such as release timing,
and some open questions surro
managed by the Flink community, as
> the
> > > amount of added features and fixies is substantial.
> > > * +1 to have the docs centralized under the Apache infra and made
> > > accessible via the main Flink docs.
> > > * +1 to make the Python SDK installable vi
+1 on the suggestion to add "What is Stateful Functions" to the left
navigation bar.
That might also mean it would be nice to have a slight rework to the main
image on the website, illustrating the use cases of Flink (this one [1]).
On the image it does mention "Event-Driven Applications", but ther
nday (Mar. 16th), and
aim to have RC1 out for flink-statefun 2.0.0 by end of next week (Mar.
20th).
As for how we want to incorporate Statefun Docker image releases in
apache/flink-docker, I'll start a separate discussion thread for that.
Cheers,
Gordon
On Tue, Mar 10, 2020 at 11:11 AM Tzu-Li
Hi!
Great to see that you're interested in contributing to Apache Flink.
Since assigning you the contributor status means that you'll be able to be
assigned to JIRA tickets by committers, could you first let us know if
there's a specific ticket that you're looking towards picking up?
Cheers,
Gor
Hi devs,
Following the consensus [1] to release Stateful Functions soon with new
version as 2.0.0, I've proceeded to cut the feature branch `release-2.0`
[2] for the project.
I'll aim to create the first voting release candidate by the end of this
week (Mar. 23).
The release candidate will also c
Hi Flink devs,
As part of a Stateful Functions release, we would like to publish Stateful
Functions Docker images to Dockerhub as an official image.
Some background context on Stateful Function images, for those who are not
familiar with the project yet:
- Stateful Function images are built o
Hi everyone,
Please review and vote on the release candidate #0 for the version 2.0.0 of
Apache Flink Stateful Functions,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
**Testing Guideline**
You can find here [1] a doc that we can us
website, since the efforts
for incorporating Stateful Functions in the website is still ongoing.
On Fri, Mar 27, 2020 at 12:48 AM Tzu-Li (Gordon) Tai
wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #0 for the version 2.0.0
> of Apache Flink Stateful Functions,
open a new RC2 with only the changes to the source NOTICE and LICENSE
files.
On Fri, Mar 27, 2020 at 10:37 AM Tzu-Li (Gordon) Tai
wrote:
> Also, here is the documentation for Stateful Functions for those who were
> wondering:
> master - https://ci.apache.org/projects/flink/flink-statefu
Hi everyone,
Please review and vote on the release candidate #2 for the version 2.0.0 of
Apache Flink Stateful Functions,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
**Testing Guideline**
You can find here [1] a doc that we can us
This vote is cancelled.
Please see the voting thread for the new candidate, RC2:
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Apache-Flink-Stateful-Functions-Release-2-0-0-release-candidate-2-td39379.html
On Fri, Mar 27, 2020 at 2:39 PM Tzu-Li (Gordon) Tai
wrote:
>
It seems the NOTICE file is missing in the
> `statefun-ridesharing-example-simulator` module while it bundles
> dependencies like
> `org.springframework.boot:spring-boot-loader:2.1.6.RELEASE`.
>
> Best,
> Hequn
>
> On Fri, Mar 27, 2020 at 3:35 PM Tzu-Li (Gordon) Tai
> wrote
those are addressed.
On Sat, Mar 28, 2020 at 1:34 AM Tzu-Li (Gordon) Tai
wrote:
> Hi Hequn,
>
> That's a good catch.
>
> Unfortunately, the spring boot dependency there, while itself being ASLv2
> licensed, pulls in other dependencies that are not ASLv2.
> That would
Hi everyone,
Please review and vote on the *release candidate #3* for the version 2.0.0
of Apache Flink Stateful Functions,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
**Testing Guideline**
You can find here [1] a doc that we can
All blockers are resolved.
This vote thread is cancelled.
There is a new vote thread for RC3:
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Apache-Flink-Stateful-Functions-Release-2-0-0-release-candidate-3-td39424.html
On Sat, Mar 28, 2020 at 7:00 PM Tzu-Li (Gordon) Tai
[1]. Should we make them consistent?
>
> Best,
> Hequn
>
> [1] https://dist.apache.org/repos/dist/dev/flink/flink-statefun-2.0.0-rc3/
>
>
> On Sun, Mar 29, 2020 at 3:31 PM Tzu-Li (Gordon) Tai
> wrote:
>
> > Hi everyone,
> >
> > Please review and vote on the *relea
On Mon, Mar 30, 2020 at 12:00 AM Tzu-Li (Gordon) Tai
wrote:
> @Hequn Cheng
> Good catches again!
>
> Regarding the incorrect versions:
> I think technically those would not be hard blockers, since what matters
> is their inclusion and licenses being acknowledged.
> It would
@Hequn Cheng
On second thought I think it would not hurt to create a RC4 to fix the
version strings. Will fix those and create that now.
On Mon, Mar 30, 2020 at 12:06 AM Tzu-Li (Gordon) Tai
wrote:
>
>
> On Mon, Mar 30, 2020 at 12:00 AM Tzu-Li (Gordon) Tai
> wrote:
>
>>
Hi everyone,
Please review and vote on the *release candidate #4* for the version 2.0.0
of Apache Flink Stateful Functions,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
**Testing Guideline**
You can find here [1] a doc that we can
...check
>> * went through walkthrough based on local builds...check
>>
>> Cheers,
>>
>> Konstantin
>>
>>
>> On Sun, Mar 29, 2020 at 6:30 PM Igal Shilman wrote:
>>
>>> Hi @Hequn Cheng , and @Tzu-Li (Gordon) Tai
>>>
>>> I
20 at 4:18 PM Stephan Ewen wrote:
> > > >
> > > > +1 to a separate repository.
> > > >
> > > > It seems to be best practice in the docker community.
>
> > > > And since it does not add overhead, why not go with the best practice?
Repo has been created:
https://github.com/apache/flink-statefun-docker
https://gitbox.apache.org/repos/asf?p=flink-statefun-docker.git
On Mon, Mar 30, 2020 at 3:57 PM Tzu-Li (Gordon) Tai
wrote:
> Thanks for the feedbacks everyone!
> Overall, everyone who replied is positive about crea
from source...check
> * Python build from source...check
> * Went through Walkthrough based on local builds...check
>
> Cheers,
>
> Konstantin
>
> On Mon, Mar 30, 2020 at 5:52 AM Tzu-Li (Gordon) Tai
> wrote:
>
> > Hi everyone,
> >
> > Please review a
AWS ecosystem: remote Python
functions running in AWS Lambda behind AWS API Gateway, Java embedded
functions running in AWS ECS
On Tue, Mar 31, 2020 at 12:09 PM Tzu-Li (Gordon) Tai
wrote:
> FYI - I've also updated the website Downloads page to include this release.
> Please also co
t; SDK Walkthrough
> > - Flink Harness works in IDE
> > - Test remote functions deployment mode with AWS ecosystem: remote Python
> > functions running in AWS Lambda behind AWS API Gateway, Java embedded
> > functions running in AWS ECS
> >
> > On Tue, Mar 31, 2020
h the original voting end time, since nothing is really touched, only
excluding some files from the staging Maven repository.
On Tue, Mar 31, 2020 at 2:29 PM Tzu-Li (Gordon) Tai
wrote:
> Hi Robert,
>
> I think you're right. There should be no tarballs / jars packaged for
> statefun
101 - 200 of 847 matches
Mail list logo
