Apart from a technical explanation, the initial suggestion does not propose how
the repository should be split up. The only meaningful split I see is for the
connectors.
This discussion dates back a few years:
https://lists.apache.org/thread.html/4ee502667a5801d23d76a01406e747e1a934417dc67ef7d2
I'm a bit late to the discussion here. Three suggestions:
1) Procedure for "insufficient active binding voters to reach 2/3 majority
> 1. Wait until the minimum length of the voting passes.
> 2. Publicly reach out to the remaining binding voters in the voting mail
> thread for at least 2
t; expect an important action like this to require a 2/3 majority.
>>
>> Personally I think consensus is good enough here. PMC members can cast a
>> veto if they disagree about the removal. In some sense, it is more
>> difficult than with 2/3 majority to remove a committer / PMC
+1 It's good that we formalize this.
On 13.08.19 10:41, Fabian Hueske wrote:
> +1 for the proposed bylaws.
> Thanks for pushing this Becket!
>
> Cheers, Fabian
>
> Am Mo., 12. Aug. 2019 um 16:31 Uhr schrieb Robert Metzger <
> rmetz...@apache.org>:
>
> > I changed the permissions of the page.
> >
>
Hi Jincheng,
+1 I would be for a 1.8.2 release such that we can fix the problems with
the nested closure cleaner which currently block 1.8.1 users with Beam:
https://issues.apache.org/jira/browse/FLINK-13367
Thanks,
Max
On 30.08.19 11:25, jincheng sun wrote:
Hi Flink devs,
It has been near
+1
On Tue, Apr 25, 2023 at 5:24 PM David Morávek wrote:
>
> Hi Eric,
>
> this sounds reasonable, there are definitely cases where you need to limit
> sink parallelism for example not to overload the storage or limit the
> number of output files
>
> +1
>
> Best,
> D.
>
> On Sun, Apr 23, 2023 at 1:
If we ban Mockito imports, I can still write tests using the full
qualifiers, right?
For example:
org.mockito.Mockito.when(somethingThatShouldHappen).thenReturn(somethingThatNeverActuallyHappens)
Just kidding, +1 on the proposal.
-Max
On Wed, Apr 26, 2023 at 9:02 AM Panagiotis Garefalakis
Thanks for starting the discussion, Jark and Xingtong!
Flink 2.0 is long overdue. In the past, the expectations for such a
release were unreasonably high. I think everybody had a different
understanding of what exactly the criteria were. This led to releasing
18 minor releases for the current majo
+1 (binding)
1. Downloaded the archives, checksums, and signatures
2. Verified the signatures and checksums
3. Extract and inspect the source code for binaries
4. Verified license files / headers
5. Compiled and tested the source code via mvn verify
6. Deployed helm chart to test cluster
7. Ran ex
Niceee. Thanks for managing the release, Gyula!
-Max
On Wed, May 17, 2023 at 8:25 PM Márton Balassi wrote:
>
> Thanks, awesome! :-)
>
> On Wed, May 17, 2023 at 2:24 PM Gyula Fóra wrote:
>>
>> The Apache Flink community is very happy to announce the release of Apache
>> Flink Kubernetes Operato
+1
On Mon, Jul 17, 2023 at 10:45 AM Chesnay Schepler wrote:
>
> +1
>
> On 16/07/2023 08:10, Mohan, Deepthi wrote:
> > @Chesnay
> >
> > Thank you for your feedback.
> >
> > An important takeaway from the previous discussion [1] and your feedback
> > was to keep the design and text/diagram changes
+1
On Tue, Jul 18, 2023 at 12:29 PM Gyula Fóra wrote:
>
> +1
>
> On Tue, 18 Jul 2023 at 12:12, Xintong Song wrote:
>
> > +1
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Tue, Jul 18, 2023 at 4:25 PM Chesnay Schepler
> > wrote:
> >
> > > The endpoint hasn't been working for years and was only
Hi Chesnay,
+1 Sounds good to me!
-Max
On Tue, Jul 18, 2023 at 10:59 AM Chesnay Schepler wrote:
>
> MetricGroup#getAllVariables returns all variables associated with the
> metric, for example:
>
> | = abcde|
> | = ||0|
>
> The keys are surrounded by brackets for no particular reason.
>
> In vir
Hi Daren,
The behavior is consistent with the regular FlinkDeployment where the
cleanup will also cancel any running jobs. Are you intending to
recover jobs from another session cluster?
-Max
On Mon, Jul 17, 2023 at 4:48 PM Wong, Daren
wrote:
>
> Hi devs,
>
> I would like to enquire about the c
+1 (binding)
1. Downloaded the source and helm archives, checksums, and signatures
2. Verified the signatures and checksums
3. Extract and inspect the source code for binaries
4. Compiled and tested the source code via mvn verify
5. Verified license files / headers
6. Deployed helm chart to test c
Hi Rui,
Thanks for the proposal. I think it makes a lot of sense to decouple
the autoscaler from Kubernetes-related dependencies. A couple of notes
when I read the proposal:
1. You propose AutoScalerEventHandler, AutoScalerStateStore,
AutoScalerStateStoreFactory, and AutoScalerEventHandler.
Autos
d release helm chart, docker image
> - Verified doc build, links
> - Ran basic stateful example, upgrade, savepoint. Checked logs, no errors
>
> Gyula
>
> On Mon, Jul 31, 2023 at 2:24 PM Maximilian Michels wrote:
>
> > +1 (binding)
> >
> > 1. Downloaded th
Congrats, well done, and welcome to the PMC Matthias!
-Max
On Tue, Aug 8, 2023 at 8:36 AM yh z wrote:
>
> Congratulations, Matthias!
>
> Best,
> Yunhong Zheng (Swuferhong)
>
> Ryan Skraba 于2023年8月7日周一 21:39写道：
>
> > Congratulations Matthias -- very well-deserved, the community is lucky to
> > h
+1 (binding)
-Max
On Tue, Aug 8, 2023 at 10:56 AM Etienne Chauchot wrote:
>
> Hi all,
>
> As part of Flink bylaws, binding votes for FLIP changes are active
> committer votes.
>
> Up to now, we have only 2 binding votes. Can one of the committers/PMC
> members vote on this FLIP ?
>
> Thanks
>
>
+1 (binding)
1. Downloaded the archives, checksums, and signatures
2. Verified the signatures and checksums
3. Extract and inspect the source code for binaries
4. Compiled and tested the source code via mvn verify
5. Verified license files / headers
6. Deployed helm chart to test cluster
7. Ran ex
Hi Gyula,
+1 The proposed changes make sense and are in line with what is
available for other metrics, e.g. number of records processed.
-Max
On Tue, Sep 5, 2023 at 2:43 PM Gyula Fóra wrote:
>
> Hi Devs,
>
> I would like to start a discussion on FLIP-361: Improve GC Metrics [1].
>
> The current
gt; handlerScalingFailure/handlerScalingReport (one of the
>> handles the event of scale failure, and the other handles
>> the event of scale success).
>>
>>
>>
>> --
>>
>> Best,
>> Matt Wang
>>
>>
>> Replied Message
>
Sep 5, 2023 at 8:13 AM Gyula Fóra wrote:
> >
> > > Hi All!
> > >
> > > @Maximilian Michels has raised the question of Flink
> > > version support in the operator before the last release. I would like to
> > > open this discussion pu
aise a pull request
> > (PR) for YARN as well.
> >
> > Our initial approach was to create a decoupled interface as part of
> > FLIP-334 and then implement it for YARN in the subsequent phase.
> > However, if you recommend combining both phases, we can certainly consi
+1 (binding)
On Wed, Sep 13, 2023 at 12:28 PM Gyula Fóra wrote:
>
> +1 (binding)
>
> Gyula
>
> On Wed, 13 Sep 2023 at 09:33, Matt Wang wrote:
>
> > Thank you for driving this FLIP,
> >
> > +1 (non-binding)
> >
> >
> > --
> >
> > Best,
> > Matt Wang
> >
> >
> > Replied Message
> > | Fro
+1 (binding)
On Thu, Sep 14, 2023 at 4:26 AM Venkatakrishnan Sowrirajan
wrote:
>
> +1 (non-binding)
>
> On Wed, Sep 13, 2023, 6:55 PM Matt Wang wrote:
>
> > +1 (non-binding)
> >
> >
> > Thanks for driving this FLIP
> >
> >
> >
> >
> > --
> >
> > Best,
> > Matt Wang
> >
> >
> > Replied Messa
Hey Rui,
+1 for making exponential backoff the default. I agree with Konstantin
that retrying forever is a good default for exponential backoff
because oftentimes the issue will resolve eventually. The purpose of
exponential backoff is precisely to continue to retry without causing
too much load.
+1 (binding)
1. Downloaded the archives, checksums, and signatures
2. Verified the signatures and checksums ( gpg --recv-keys
B2D64016B940A7E0B9B72E0D7D0528B28037D8BC )
3. Extract and inspect the source code for binaries
4. Compiled and tested the source code via mvn verify
5. Verified license fil
Have a great time off, Etienne!
On Thu, Oct 26, 2023 at 3:38 PM Etienne Chauchot wrote:
>
> Hi,
>
> FYI, I'll be off and unresponsive for a week starting tomorrow evening.
> For ongoing work, please ping me before tomorrow evening or within a week
>
> Best
>
> Etienne
+1 for targeting the release as soon as possible. Given the effort
that Rui has undergone to decouple the autoscaling implementation, it
makes sense to also include an alternative implementation with the
release. In the long run, I wonder whether the standalone
implementation should even be part of
Hi Mason,
Thank you for the proposal. This is a highly requested feature to make
the source scaling of Flink Autoscaling generic across all sources.
The current implementation handles every source individually, and if
we don't find any backlog metrics, we default to using busy time only.
At this p
+1 (binding)
1. Downloaded the archives, checksums, and signatures
2. Verified the signatures and checksums
3. Extract and inspect the source code for binaries
4. Compiled and tested the source code via mvn verify
5. Verified license files / headers
6. Deployed helm chart to test cluster
7. Build
Thanks for reviving the efforts here Matthias! +1 for the transition
to GitHub Actions.
As for ASF Infra Jenkins, it works fine. Jenkins is extremely
feature-rich. Not sure about the spare capacity though. I know that
for Apache Beam, Google donated a bunch of servers to get additional
build capac
+1 (binding)
-Max
On Thu, Nov 30, 2023 at 9:15 AM Rui Fan <1996fan...@gmail.com> wrote:
>
> +1(binding)
>
> Best,
> Rui
>
> On Mon, Nov 13, 2023 at 11:01 AM Rui Fan <1996fan...@gmail.com> wrote:
>
> > Hi everyone,
> >
> > Thank you to everyone for the feedback on FLIP-364: Improve the
> > restart
Thank you Rui for driving this!
On Thu, Nov 30, 2023 at 3:01 AM Rui Fan <1996fan...@gmail.com> wrote:
>
> The Apache Flink community is very happy to announce the release of
> Apache Flink 1.16.3, which is the
> third bugfix release for the Apache Flink 1.16 series.
>
>
>
> Apache Flink® is an ope
Hey Rui,
+1 for changing the default restart strategy to exponential-delay.
This is something all users eventually run into. They end up changing
the restart strategy to exponential-delay. I think the current
defaults are quite balanced. Restarts happen quickly enough unless
there are consecutive
;
> Looking forward to your feedback, thanks~
>
> [1] https://github.com/apache/flink/pull/23247#discussion_r1422626734
> [2]
> https://github.com/apache/flink/assets/38427477/642c57e0-b415-4326-af05-8b506c5fbb3a
> [3] https://issues.apache.org/jira/browse/FLINK-33736
>
> Bes
+1 (binding)
On Tue, Dec 12, 2023 at 2:23 PM Peter Huang wrote:
>
> +1 Non-binding
>
>
> Peter Huang
>
> Őrhidi Mátyás 于2023年12月12日 周二下午9:14写道：
>
> > +1
> > Matyas
> >
> > On Mon, Dec 11, 2023 at 10:26 PM Gyula Fóra wrote:
> >
> > > +1
> > >
> > > Gyula
> > >
> > > On Mon, Dec 11, 2023 at 1:26 P
Hi Rui,
+1 for removing the @Deprecated annotation from `getString(String key,
String defaultValue)`. I would remove the other typed variants with
default values but I'm ok with keeping them if they are still used.
-Max
On Wed, Dec 13, 2023 at 4:59 AM Rui Fan <1996fan...@gmail.com> wrote:
>
> Hi
> Anyone for pushing my pub key to apache dist ?
Done.
On Thu, Dec 21, 2023 at 2:36 PM Etienne Chauchot wrote:
>
> Hello,
>
> All the ongoing PRs on this repo were merged. But, I'd like to leave
> some more days until feature freeze in case someone had a feature ready
> to integrate.
>
> Let' pu
Happy New Year everyone,
I'd like to start the year off by announcing Alexander Fedulov as a
new Flink committer.
Alex has been active in the Flink community since 2019. He has
contributed more than 100 commits to Flink, its Kubernetes operator,
and various connectors [1][2].
Especially notewort
x27;s unexpected IIUC.
>> Would you like to fix it?
>>
>> Feel free to create a FLINK JIRA to fix it if you would like to, and I'm
>> happy to
>> review!
>>
>> And cc @Maximilian Michels
>>
>> Best,
>> Rui
>>
&g
+1 (binding)
On Wed, Jan 10, 2024 at 11:22 AM Martijn Visser
wrote:
>
> +1 (binding)
>
> On Wed, Jan 10, 2024 at 4:43 AM Xingbo Huang wrote:
> >
> > +1 (binding)
> >
> > Best,
> > Xingbo
> >
> > Dian Fu 于2024年1月10日周三 11:35写道：
> >
> > > +1 (binding)
> > >
> > > Regards,
> > > Dian
> > >
> > > On
I'm also late to the party here :) When I saw the first draft, I was
thinking how exactly the design doc would tie in with Beam. Thanks for
the update.
A couple of comments with this regard:
Flink has provided a distributed cache mechanism and allows users to upload their files using
"regist
+1 (binding)
On 25.10.19 14:31, Congxian Qiu wrote:
+1 (non-biding)
Best,
Congxian
Terry Wang 于2019年10月24日周四 上午11:15写道：
+1 (non-biding)
Best,
Terry Wang
2019年10月24日 10:31，Jingsong Li 写道：
+1 (non-binding)
Best,
Jingsong Lee
On Wed, Oct 23, 2019 at 9:02 PM Yu Li wrote:
+1 (non-bin
.
Thanks again for your feedback, and it is valuable for find out the
final
best architecture.
Feel free to correct me if there is anything incorrect.
Best,
Jincheng
Maximilian Michels 于2019年10月16日周三 下午4:23写道：
I'm also late to the party here :) When I saw the first draft, I
was
think
Hi everyone,
I've recently come across a cluster scheduling problem users are facing.
Clusters where TaskManagers have more slots than the parallelism
(#tm_slots > job_parallelism), tend to schedule all job tasks on a
single TaskManager.
This is not good for spreading load and has been discu
ot 100% sure whether spreading out tasks is always the
best strategy. Especially if you have a network heavy job co-locating tasks
on the same TM could have benefits over spreading the tasks out.
[1] https://issues.apache.org/jira/browse/FLINK-10429
Cheers,
Till
On Thu, Oct 11, 2018 at 8:16 P
Great work! :)
Was just trying the new release out with Beam and found that
"force-shading" is not published for 1.5.5. Also visible here:
https://repo.maven.apache.org/maven2/org/apache/flink/force-shading/
Was this intentional? It is not a big problem because it is a dependency
which is on
Hi!
Do you think it would make sense to send JIRA notifications to a
separate mailing list? Some people just want to casually follow the
mailing list and it requires a filter to delete all the JIRA mails.
We already have an "issues" mailing list which receives the JIRA
notifications: https:/
g notifications only for newly created
issues.
Thanks,
Max
On 21.11.18 12:52, vino yang wrote:
+1
Flavio Pompermaier 于2018年11月21日周三 下午7:24写道：
+1
On Wed, Nov 21, 2018 at 12:05 PM Saar Bar wrote:
💯 agree
Sent from my iPhone
On 21 Nov 2018, at 13:03, Maximilian Michels wrote:
Hi!
D
Hi Chesnay,
Just saw this. I had unarchived the version because I thought it had been
archived accidentally. I have archived it again.
I hope it is ok to include this fix:
https://issues.apache.org/jira/browse/FLINK-10566
Otherwise, feel free to move it to 1.7.2.
Thanks,
Max
On 13.12.18 2
I have pushed this fix to the release-1.5 branch:
https://issues.apache.org/jira/browse/FLINK-10566
Would be great if we could include it because it has been blocking some
pipelines on the Beam side.
Thanks,
Max
On 13.12.18 20:22, Chesnay Schepler wrote:
FLINK-11023: will not be fixed for 1.
Can confirm they still go to the main comment section.
Would be great if we could send them to the Work Log instead. We do that for the
Beam JIRA project and it has proven very useful for reducing noise.
Thanks,
Max
On 13.12.18 22:15, Tzu-Li Chen wrote:
hmm..then what is it
Chesnay Scheple
Hi Xianda, hi Shaoxuan,
I'd be in favor of option (1). There is great potential in Beam and Flink
joining forces on this one. Here's why:
The Beam project spent at least a year developing a portability layer with a
reasonable amount of people working on it. Developing a new portability layer
Hi,
Has there been any progress on
https://issues.apache.org/jira/browse/FLINK-2491?
For the Flink Runner in Apache Beam we keep operators alive to avoid
checkpointing to stop working [1]. Users of Flink's native API have to
take care of this themselves.
To fix FLINK-2491 we have to:
1)
Hi Stephan,
This is excited! Thanks for sharing. The inter-process communication
code looks like the most natural choice as a common ground. To go
further, there are indeed some challenges to solve.
=> Biggest question is whether the language-independent DAG is expressive
enough to capture
lternatively, we could drop the JavaDocs rule and make the transition
>>> significantly cheaper.
>>>
>>> 2015-10-22 15:24 GMT+02:00 Till Rohrmann :
>>>
>>> > There ain’t no such thing as a free lunch and code style.
>>> >
>>> > O
Dear Flink community,
We have forked the current release candidate from the master to the
release-0.10-rc0 branch. Changes for the next release candidate should
be pushed to the release-0.10 branch. The master needed to be updated
to deploy only one snapshot version to the Maven repository and to
Great project. Thanks for sharing!
On Thu, Oct 22, 2015 at 9:29 PM, Ufuk Celebi wrote:
> Wow! Very nice. Thanks for sharing. I will try it out :-)
>
> On Thursday, October 22, 2015, Kunft, Andreas
> wrote:
>
> > FYI:
> >
> >
> > FastR on Flink, a project to combine the R programming language wi
Thanks for reporting, Suneel. On my machine the Java docs build.
Here's the build log:
https://ci.apache.org/builders/flink-docs-master/builds/122/steps/Java%20%26%20Scala%20docs/logs/stdio
[ERROR]
/home/buildslave2/slave2/flink-docs-master/build/flink-staging/flink-scala-shell/src/main/scala/o
hrm...@apache.org
> > >
> > >>>>> wrote:
> > >>>>>
> > >>>>> Forget my last mail. Just found out that the Mahout guys are still
> > >>>>>>
> > >>>>> running
> > >>>>>
Thanks Matthias for pointing this out. I opened an issue some time ago with
a similar description: https://issues.apache.org/jira/browse/FLINK-2752
I agree with Fabian and Ufuk that it makes sense to separate the website
and the source repository. However, the distinction between the
documentation
Hi Flinksters,
We have recently committed an easy way to change Flink's Scala version. The
question arises now whether we should ship Scala 2.11 as binaries and via
Maven. For the rc0, I created all binaries twice, for Scala 2.10 and 2.11.
However, I didn't create Maven artifacts. This follows our
+1 for a new RC.
> >
> > I tried to reproduce FLINK-2800 but did not succeed yet. I will spend a
> bit
> > more time on it and if we have a fix within time (before a new RC) we can
> > include it.
> >
> > 2015-10-26 10:36 GMT+01:00 Maximilian Michels :
>
Please vote on releasing the following candidate as Apache Flink version
0.10.0:
The commit to be voted on:
d4479404a9a9245ed897189973d8f6dadb9c814b
Branch:
release-0.10.0-rc1 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git)
The release artifacts to be voted on can be found at:
Saputra
wrote:
> Hi Max,
>
> Is there a way that dev@ list gets email notification if the build fail
> for
> the build bot?
>
> - Henry
>
> On Monday, October 26, 2015, Maximilian Michels wrote:
>
> > Thanks for reporting, Suneel. On my machine the Java docs
I've prepared a new testing document:
https://docs.google.com/document/d/1S3niz5dPElA4dX-SfLwf9JwkzEAYHVLD7vsLLOAu06Q/edit
Please take one or two checks and verify them. Thanks and happy testing :)
On Mon, Oct 26, 2015 at 11:06 PM, Maximilian Michels wrote:
> Please vote on relea
Thanks for spotting this, Aljoscha. The main issue are the quickstart
files. Quite odd the release scripts didn't catch that.
On Tue, Oct 27, 2015 at 12:18 PM, Ufuk Celebi wrote:
>
> > On 27 Oct 2015, at 12:12, Aljoscha Krettek wrote:
> >
> > There are still references to 0.10-SNAPSHOT in the r
2015, at 13:48, Aljoscha Krettek wrote:
> >
> > start-cluster-streaming.sh and start-local-streaming.sh don’t work if
> the flink path has spaces. I’m fixing it on master and on release-0.10.
> >> On 26 Oct 2015, at 23:06, Maximilian Michels wrote:
> >>
> >
7;t work for Safari (I left a
> note
> >> in the previous testing doc).
> >>
> >> -Vasia.
> >>
> >> On 27 October 2015 at 15:18, Maximilian Michels wrote:
> >>
> >>> Good catch, Aljoscha. As far as I know the plan visualizer is only
&g
The vote is cancelled in favor of a new release candidate.
On Tue, Oct 27, 2015 at 10:10 PM, Maximilian Michels wrote:
> Thank you all for testing so far!
>
> We fixed the version number problem. Ufuk's configuration parameters and
> shading for EMR have been pulled into the re
Please vote on releasing the following candidate as Apache Flink version
0.10.0:
The commit to be voted on:
ed75049dfc9748eae81ace9d4d686907dcd7835c
Branch:
release-0.10.0-rc2 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git)
The release artifacts to be voted on can be found at:
mail.com> wrote:
> Is there a new testing doc for rc2 or are we using the previous one?
> Thanks!
>
> On 27 October 2015 at 22:17, Maximilian Michels wrote:
>
> > Please vote on releasing the following candidate as Apache Flink version
> > 0.1
Yes, you can find lots of Flink slides on the Slideshare.
On Tue, Oct 27, 2015 at 9:46 PM, Matthias J. Sax wrote:
> Hi,
>
> I just "discovered" that on the Flink "Material" page, a couple of slide
> decks are listed (https://flink.apache.org/material.html). I guess, this
> list is far from compl
> - Cluster
> > >>> - Yarn
> > >>> - DataSet API
> > >>> - Programming guide
> > >>> - transformations
> > >>> - DataStream API
> > >>> - Programming Guide
> > >>> - Internals
> &g
d them later on.
>>
>> Please give feedback.
>>
>>
>> -Matthias
>>
>>
>>
>>
>> On 10/09/2015 03:34 PM, Maximilian Michels wrote:
>>> Yes, Community is a better place. You can also add the Dataflow Runner
>>> https://github.com
the web interface :)
> What is the "Job Accumulator/Statistics" tab supposed to show? No matter
> what job I run, the values are the same (operator=1, parallelism=2,
> subtasks=3). Are these hard-coded defaults?
>
> Thanks!
> -Vasia.
>
> On 28 October 201
:25 PM, "Vasiliki Kalavri" > >
>> > > wrote:
>> > >
>> > > > I have a question regarding the web interface :)
>> > > > What is the "Job Accumulator/Statistics" tab supposed to show? No
>> > matter
>> >
try it out. After that, we can try
>>> to come to a conclusion.
>>>
>>> I guess, together with the darker color schema on the doc page menu, the
>>> distinction between both pages should become clear.
>>>
>>> -Matthias
>>>
>>> On 10
X1VYQTlrQWNfUkE/view?usp=sharing
>> .
>> Shouldn't these numbers show tasks?
>>
>> On 28 October 2015 at 14:26, Maximilian Michels wrote:
>>
>> > @Vasia:
>> >
>> > - There are two types of shapes which are colored :) The circles mark
&
;>>
>>> See
>>>
>>> https://drive.google.com/file/d/0BzQJrI2eGlyYMHZZUGs2ZFJzaXc/view?usp=sharing
>>> vs.
>>>
>>> https://drive.google.com/file/d/0BzQJrI2eGlyYc3kzMlQ4OXN6a3c/view?usp=sharing
>>>
>>> -Vasia.
>>&
nk-dist first. :)]
>>
>>
>>
>> -- Sachin Goel
>> Computer Science, IIT Delhi
>> m. +91-9871457685
>>
>> On Wed, Oct 28, 2015 at 8:22 PM, Vasiliki Kalavri <
>> vasilikikala...@gmail.com> wrote:
>>
>>> Ah I see. Thanks Sachi
t; m. +91-9871457685
>
> On Wed, Oct 28, 2015 at 9:42 PM, Maximilian Michels wrote:
>
>> @Sachin: I've tried it out. It has the tendency to make things a bit
>> harder to read (because it breaks words at arbitrary positions).
>> However, we don't have a bett
The issue with our Java Docs has been resolved. The link works again.
On Tue, Oct 27, 2015 at 3:57 PM, Henry Saputra wrote:
> Ah thanks Max, sending to commits@ is good
>
> - Henry
>
> On Tue, Oct 27, 2015 at 2:35 AM, Maximilian Michels wrote:
>> Hi Henry,
>>
>>
Hi Andra,
What you thought of turns out to be one of the core features of the Flink
streaming API. Flink's operators support state. State can be partitioned by
the the key using keyBy(field).
You may use a MapFunction to achieve what you wanted like so:
public static void main(String[] args) th
: "+ counter.value() +
" Update state to: "+ value.f1);
counter.update(value.f1);
return value;
}
@Override
public void open(Configuration config) {
counter = getRuntimeContext().getKeyValueState("mystate",
Long.class, -1L);
}
}
On Wed,
built with Scala 2.10. As a
>>>>>
>>>> consequence,
>>>>
>>>>> they mix flink dependencies with other dependencies pulling in Scala
>>>>>
>>>> 2.11
>>>
>>>> and then they wonder that the progra
Hi Greg,
Thanks for reporting. You wrote you didn't see any output in the .out files
of the task managers. What about the .log files of these instances?
Where and when did you produce the thread dump you included?
Thanks,
Max
On Thu, Oct 29, 2015 at 1:46 PM, Greg Hogan wrote:
> I am testing a
Hi Matthias,
There is currently no cancel button in the web frontend. Just filed this
ticket today: https://issues.apache.org/jira/browse/FLINK-2939
Cheers,
Max
On Thu, Oct 29, 2015 at 4:49 PM, Matthias J. Sax wrote:
> Hi,
>
> I was just playing with the new JobManager web frontend and missing
. I just found a serious issue with the KryoSerializer
> (FLINK-2800) which in some cases produced duplicated elements or corrupted
> data. I opened a PR to fix the issue (
> https://github.com/apache/flink/pull/1308).
>
> Cheers,
> Till
>
>
> On Wed, Oct 28, 2015 at 5:38 P
This vote is cancelled in favor of a new RC.
On Fri, Oct 30, 2015 at 9:03 AM, Maximilian Michels wrote:
> Thanks for reporting and providing a fix, Till! We have also fixed two
> issues with the new job manager web frontend and pushed them to the
> release-0.10 branch. Please rev
Please vote on releasing the following candidate as Apache Flink version
0.10.0:
The commit to be voted on:
2cd5a3c05ceec7bb9c5969c502c2d51b1ec00d0c
Branch:
release-0.10.0-rc3 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git)
The release artifacts to be voted on can be found at:
For testing, please refer to this document:
https://docs.google.com/document/d/1OtiAwILpnIwCqPF1Sk_8EcXuJOVc4uYtlP4i8m2c9rg/edit
On Fri, Oct 30, 2015 at 9:05 AM, Maximilian Michels wrote:
> Please vote on releasing the following candidate as Apache Flink version
> 0.10.0:
>
> The
t java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>
> This happens on OSX and Windows 10 with Cygwin.
>
> 2015-10-30 10:47 GMT+01:00 Maximilian Michels :
>
> > For testing, please refer to this document:
> >
> >
> https://docs.google.com/document/d/1OtiA
This vote is cancelled in favor of a new RC.
On Fri, Oct 30, 2015 at 12:06 PM, Maximilian Michels wrote:
> Hmpf. Just looked into this. In the Hadoop 2.X Scala 2.11 jar, Curator is
> not shaded. Thus, it fails to load the shaded classes. After we fix this,
> we will have to create
Please vote on releasing the following candidate as Apache Flink version
0.10.0:
The commit to be voted on:
6044b7f0366deec547022e4bc40c49e1b1c83f28
Branch:
release-0.10.0-rc4 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git)
The release artifacts to be voted on can be found at:
We can continue testing now:
https://docs.google.com/document/d/1keGYj2zj_AOOKH1bC43Xc4MDz0eLhTErIoxevuRtcus/edit
On Fri, Oct 30, 2015 at 3:49 PM, Maximilian Michels wrote:
> Please vote on releasing the following candidate as Apache Flink version
> 0.10.0:
>
> The commit to
ote -1 if we keep tabs.
>>
>>
>>
>> On Sat, Oct 24, 2015 at 8:33 PM, Henry Saputra
>> wrote:
>>
>> > +1 for adding restriction for Javadoc at least at the header of public
>> > classes and methods.
>> >
>> > We did the exercise in T
appear for the stable release.
>
>
> 2015-10-29 11:58 GMT+01:00 Maximilian Michels :
>
>> Seems like we agree that we need artifacts for different versions of Scala
>> on Maven. There also seems to be a preference for including the version in
>> the artifact name.
>
1 - 100 of 847 matches
Mail list logo
