Ufuk Celebi created FLINK-35038:
---
Summary: Bump test dependency org.yaml:snakeyaml to 2.2
Key: FLINK-35038
URL: https://issues.apache.org/jira/browse/FLINK-35038
Project: Flink
Issue Type
Hey all,
I'd like to join the release managers for 1.20 as well. I'm looking forward to
getting more actively involved again.
Cheers,
Ufuk
On Sun, Mar 24, 2024, at 11:27 AM, Ahmed Hamdy wrote:
> +1 for the proposed timeline and release managers.
> Best Regards
> Ahmed Hamdy
>
>
> On Fri, 22
+1 (binding)
– Ufuk
On Mon, Jan 15, 2024, at 12:38 PM, Congxian Qiu wrote:
> +1 (non-binding)
>
> Best,
> Congxian
>
>
> Gyula Fóra 于2024年1月15日周一 15:37写道：
>
> > +1 (binding)
> >
> > On Sun, Jan 14, 2024 at 9:01 AM Yun Tang wrote:
> >
> > > +1 (non-binding)
> > >
> > > On 2024/01/14
Ufuk Celebi created FLINK-21928:
---
Summary: DuplicateJobSubmissionException after JobManager failover
Key: FLINK-21928
URL: https://issues.apache.org/jira/browse/FLINK-21928
Project: Flink
t; >> > be
> >> > >>>>> concerned about (where you have lots of variables) I would think
> >> that
> >> > >>>>> this is a deal-breaker.
> >> > >>>>>
> >> > >>>>> On 1/26/2021 2:59 PM, Kh
+1
On Wed, Jan 27, 2021, at 11:02 AM, Dawid Wysakowicz wrote:
> +1
>
> On 27/01/2021 11:00, Chesnay Schepler wrote:
> > +1
> >
> > While I don't think the filesystem is really useless, in it's current
> > state it is not maintainable, and so far no one rose up to remedy this.
> >
> > On
@Xingtong: The assumption for the mapping was that we only have dots and
hyphens in the keys. Do you have an example for a key which include
underscores? If underscores are common for keys (I couldn't find any existing
options that use it), it would certainly be a blocker for the discussed
I'm including Steven and Yang into this discussion (cc'd) who raised some good
points in the initial DISCUSS thread. Do you have any opinion on the current
discussion here?
On Tue, Jan 26, 2021, at 10:59 AM, Ufuk Celebi wrote:
> Chesnay, thanks for bringing this up. I think it's an alternat
> be set on the command-line?
> > > >>
> > > >> What use-case do they currently not support?
> > > >> I assume it's something along the lines of setting some environment
> > > >> variable for containers, but at le
LGTM. Let's see what the others think...
On Thu, Jan 21, 2021, at 11:37 AM, Ingo Bürk wrote:
> Regarding env.java.opts, what special handling is needed there? AFAICT only
> the rejected alternative of substituting values would've had an effect on
> this.
Makes sense
>From the FLIP:
> This
Thanks for starting the discussion, Ingo!
Regarding approach 1:
I like the idea of having a mapping scheme from ConfigOption to env var(s), but
I'm concerned about the implications of lazy eval. I think it would be
preferable to keep the Configuration object as the source of truth, requiring
Congrats and welcome! :-)
On Wed, Jan 20, 2021, at 9:57 AM, Cranmer, Danny wrote:
> Congratulations Guowei!!
>
> On 20/01/2021, 05:35, "Kurt Young" wrote:
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm
Hey all,
I think that approach 2 is more idiomatic for container deployments where it
can be cumbersome to manually map flink-conf.yaml contents to env vars [1]. The
precedence order outlined by Till would also cover Steven's hierarchical
overwrite requirement.
I'm really excited about this
+1 to do this. I really like what you have build and the advantages to Jekyll
seem overwhelming to me. Hugo is very flexible and I've seen a few other
projects use it successfully for docs.
On Wed, Jan 13, 2021, at 5:14 PM, Seth Wiesman wrote:
> Hi All,
>
> I would like to start a discussion
+1 (binding)
Thanks Yun for debugging and running the benchmarks.
– Ufuk
On Fri, Nov 6, 2020 at 3:49 PM Fabian Paul
wrote:
> +1 (non-binding)
>
> Thanks, Yun for the efforts to bring this topic to a vote.
>
> Best,
> Fabian
>
+1 (binding)
- checked release notes ✅
- verified signatures and checksums ✅
- reviewed website PR ✅
- built an internal Flink distribution from source ✅
- built internal jobs against the staging repo ✅
- deployed a job cluster on Kubernetes and tested checkpointing ✅
- tested fix for FLINK-18902
Congrats! :-)
– Ufuk
On Thu, Jun 18, 2020 at 9:47 AM Marta Paes Moreira
wrote:
> Awesome! Congratulations, Yu!
>
> On Thu, Jun 18, 2020 at 9:16 AM Zhu Zhu wrote:
>
> > Congratulations!
> >
> > Thanks,
> > Zhu Zhu
> >
> > Guowei Ma 于2020年6月18日周四 上午10:41写道：
> >
> > > Congratulations , Yu!
> >
I agree with Konstantin and Steven that it makes sense to point this out
explicitly.
I think that the following would be helpful:
1/ Mention breaking compatibility in release notes
2/ Update the linked table to reflect compatibilities while pointing out
what the community commits to maintain
I agree with Till. I think this should be a concern of the user configuring
the port range.
– Ufuk
On Mon, May 25, 2020 at 10:27 AM Till Rohrmann wrote:
> Hi Weike,
>
> would it be good enough if the user did not include unsafe ranges when
> specifying `rest.bind-port`? My concern with
+1
– Ufuk
On Fri, May 15, 2020 at 4:54 PM Zhijiang
wrote:
> Sounds good, +1.
>
> Best,
> Zhijiang
>
>
> --
> From:Thomas Weise
> Send Time:2020年5月15日(星期五) 21:33
> To:dev
> Subject:Re: [VOTE] Guarantee that @PublicEvolving
Thanks for the analysis Till.
1/ I think breaking binary compatibility is acceptable between minor
releases (1.10 -> 1.11) as you suggested since the API is marked
as @PublicEvolving.
2/ I'm quite torn about how to proceed with the 1.10.x patch release, but
slightly leaning towards the
+1 (binding)
- checked release notes
- verified sums and hashes
- reviewed website PR
- successfully built an internal Flink distribution based on the 1.10.1-rc3
commit
- successfully built internal jobs against the staging repo and deployed
those jobs to a 1.10.1 job cluster on Kubernetes and
Hey Robert and others,
overall +1 to support Hadoop 3. It would be a great to unblock Flink
support in EMR 6.0 as noted in the linked FLINK ticket.
The arguments raised against flink-shaded-hadoop make sense to me. I have a
few general questions still:
1) Will the flink-shaded-hadoop module (in
Ufuk Celebi created FLINK-17500:
---
Summary: Deploy JobGraph form file in StandaloneClusterEntrypoint
Key: FLINK-17500
URL: https://issues.apache.org/jira/browse/FLINK-17500
Project: Flink
Issue
+1 (binding)
- checked release notes ✅
- verified sums and hashes ✅
- verified no binary artifacts in source release ✅
- reviewed website PR ✅
- built from source ✅
- built an internal Flink distribution based on the 1.9.3-rc1 commit ✅
- built internal jobs against the staging repo ✅
- deployed
Thanks for starting this FLIP.
+1
On Tue, Apr 7, 2020 at 11:29 AM Andrey Zagrebin
wrote:
> Hi All,
>
> As discussed in these threads [1] and [2],
> we suggest to unify the docker topic in Flink for users [3].
>
> This mainly means refactoring of the existing code and introducing more
> docs as
; # Dockerfile / image for developers
> We keep it on our future roadmap. This effort should help to understand
> what we can reuse there.
>
> Best,
> Andrey
>
>
> On Fri, Apr 3, 2020 at 12:57 PM Till Rohrmann
> wrote:
>
>> Hi everyone,
>>
>&
Hey Yang,
thanks! See inline answers.
On Fri, Apr 3, 2020 at 5:11 AM Yang Wang wrote:
> Hi Ufuk,
>
> Thanks for make the conclusion and directly point out what need to be done
> in
> FLIP-111. I agree with you that we should narrow down the scope and focus
> the
> most important and basic part
Hey all,
thanks for the proposal and the detailed discussion. In particular, thanks
to Andrey for starting this thread and to Patrick for the additional ideas
in the linked Google doc.
I find many of the improvements proposed during the discussion (such as the
unified entrypoint in Flink, proper
+1.
The repo creation process is a light-weight, automated process on the ASF
side. When Patrick Lucas contributed docker-flink back to the Flink
community (as flink-docker), there was virtually no overhead in creating
the repository. Reusing build scripts should still be possible at the cost
of
;>>>> - Cluster partitions
> > >>>>>>>> - Memory configuration
> > >>>>>>>> - Recovery
> > >>>>>>>>
> > >>>>>>>> Cheers,
> > >>>>>>>> Till
> > &g
I'd be happy to read such a blog. Big +1 as a potential reader. ;-)
– Ufuk
On Mon, Mar 2, 2020 at 11:53 AM Arvid Heise wrote:
> Dear devs,
>
> development speed of Flink has steadily increased. Lots of new concepts are
> introduced and technical debt removed. However, it's hard to keep track
PS: Also verified the NOTICE changes since the last RC.
On Thu, Feb 13, 2020 at 5:25 PM Ufuk Celebi wrote:
> Hey Chensay,
>
> +1 (binding).
>
> - Verified checksum ✅
> - Verified signature ✅
> - Jira changelog looks good to me ✅
> - Website PR looks good to me ✅
Hey Chensay,
+1 (binding).
- Verified checksum ✅
- Verified signature ✅
- Jira changelog looks good to me ✅
- Website PR looks good to me ✅
- Verified no unshaded dependencies (except the Hadoop modules which I
think is expected) ✅
- Verified dependency management fix FLINK-15540
+1 to have the README as source of truth and link to the repository from
the Wiki page.
– Ufuk
On Mon, Feb 10, 2020 at 3:48 AM Yang Wang wrote:
> +1 to make flink-docker repository self-contained, including the document.
> And others refer
> to it.
>
>
> Best,
> Yang
>
> Till Rohrmann
Ufuk Celebi created FLINK-15831:
---
Summary: Add Docker image publication to release documentation
Key: FLINK-15831
URL: https://issues.apache.org/jira/browse/FLINK-15831
Project: Flink
Issue
Ufuk Celebi created FLINK-15830:
---
Summary: Migrate docker-flink/docker-flink to apache/flink-docker
Key: FLINK-15830
URL: https://issues.apache.org/jira/browse/FLINK-15830
Project: Flink
Issue
Ufuk Celebi created FLINK-15829:
---
Summary: Request apache/flink-docker repository
Key: FLINK-15829
URL: https://issues.apache.org/jira/browse/FLINK-15829
Project: Flink
Issue Type: Sub-task
Hi everyone,
I'm happy to announce that we have unanimously approved the integration of
the Docker image publication into the Flink release process.
+1s (17 votes in total, 6 binding, 11 non-binding):
- Till Rohrmann (binding)
- Stephan Ewen (binding)
- Fabian Hüske (binding)
- Konstantin Knauf
Ufuk Celebi created FLINK-15828:
---
Summary: Integrate docker-flink/docker-flink into Flink release
process
Key: FLINK-15828
URL: https://issues.apache.org/jira/browse/FLINK-15828
Project: Flink
; >>>> for every Flink release.
> > > >>>> Since we're mainly migrating the docker-flink/docker-flink repo to
> > > >>>> apache/flink-docker, this should just work as before.
> > > >>>>
> > > >>>> Less important images (playgr
Hey all,
there is a proposal to contribute the Dockerfiles and scripts of
https://github.com/docker-flink/docker-flink to the Flink project. The
discussion corresponding to this vote outlines the reasoning for the
proposal and can be found here: [1].
The proposal is as follows:
* Request a new
t; main Flink images (those that depend on Flink releases) for better
> > visibility and to not confuse our users.
> > We might want to publish less critical images (playground images, dev
> > images, nightly builds, etc) via Infra under the Apache DockerHub user.
> >
>
Hey all,
first of all a big thank you for driving many of the Docker image releases
in the last two years.
*(1) Moving docker-flink/docker-flink to apache/docker-flink*
+1 to do this as you outlined. I would propose to aim for a first
integration with the 1.10 release without major changes to
I can confirm that the Docker images are available [1]. Thanks, Patrick!
Looking forward to your ideas to integrate the Docker builds into the
release process. I'm happy to support you on this effort.
– Ufuk
[1] $ docker pull flink:1.8.3
1.8.3: Pulling from library/flink
844c33c7e6ea: Pull
Answers inline...
On Thu, Dec 5, 2019 at 6:28 PM Seth Wiesman wrote:
> One option would be to do exactly that, but then I feel like we are
> committing to tracking changes on those systems and I just don't know how
> feasible that is.
>
I don't think that's feasible. It's bound to get out of
+1 (binding)
* verified checksums and hashes
* ran stateful example job in Kubernetes environment
* build (custom) Docker image from sources for Scala 2.11, 2.12
* used jackson new 2.10.1 profile and verified that the jackson databind
version is updated
* verified versions match 1.8.3 in pom.xml
+1 to drop the MapR page.
For the other two I'm +0. I fully agree that the linked AWS and GCE pages
are in bad shape and don't relate to a component developed by the
community. Do we have any numbers from Google Analytics on how popular
those pages are? If they are somewhat popular, I would
can cause severe
> >> performance issues for large scale jobs. So I hope the fix could be
> >> released with 1.8.3.
> >>
> >> The fix is already merged into master, and is now in the process of
> >> backporting to 1.8.
> >>
> >> Thanks,
+1 (binding)
* built master against flink-shaded 9.0 and jackson 2.10.1 (via
https://repository.apache.org/content/repositories/orgapacheflink-1275)
- code: https://github.com/uce/flink/tree/flink-shaded-9.0
- travis: https://travis-ci.org/uce/flink/builds/615013399
* ran examples against web
ese security vulnerabilities.
>
> Thanks a lot for your nice work and kick off the release so quickly.
>
>
> On Fri, Nov 15, 2019 at 11:50 PM Ufuk Celebi wrote:
>
> > From what I can see, the Jackson version bump fixes quite a few
> > vulnerabilities. Theref
rade does not have to be
> >>>> part of the profile; since it is only intended for internal use anyway
> >>>> (and thus has limited exposure) we can be pretty sure this doesn't
> break
> >>>> anything.
> >>>>
> >>>> On 15/1
>From what I can see, the Jackson version bump fixes quite a few
vulnerabilities. Therefore, I'd be +1 to release flink-shaded 9.0.
Thanks for all the work to verify this on master already.
– Ufuk
On Fri, Nov 15, 2019 at 2:26 PM Chesnay Schepler wrote:
> Hello,
>
> I'd like to kick off the
The opt-in approach seems reasonable to me. +1 to include the profiles in
1.8 and 1.9 without changing the default versions (including the default
version of flink-shaded).
As far as I can tell, the next steps would be:
1) Release flink-shaded with upgraded Jackson
2a) Bump the flink-shaded
+1 (binding)
On Fri, Oct 25, 2019 at 6:39 PM Maximilian Michels wrote:
> +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
> >>
> >>
> >>
>
Ufuk Celebi created FLINK-14145:
---
Summary: getLatestCheckpoint returns wrong checkpoint
Key: FLINK-14145
URL: https://issues.apache.org/jira/browse/FLINK-14145
Project: Flink
Issue Type: Bug
I'm late to the party... Welcome and congrats! :-)
– Ufuk
On Mon, Aug 19, 2019 at 9:26 AM Andrey Zagrebin
wrote:
> Hi Everybody!
>
> Thanks a lot for the warn welcome!
> I am really happy about joining Flink committer team and hope to help the
> project to grow more.
>
> Cheers,
> Andrey
>
>
+1 (binding)
– Ufuk
On Wed, Aug 14, 2019 at 4:50 AM Biao Liu wrote:
> +1 (non-binding)
>
> Thanks for pushing this!
>
> Thanks,
> Biao /'bɪ.aʊ/
>
>
>
> On Wed, 14 Aug 2019 at 09:37, Jark Wu wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Jark
> >
> > On Wed, 14 Aug 2019 at 09:22, Kurt Young
Thanks for checking. No concerns on my side. +1 to back port. Fixing fault
tolerance of streaming iterations sounds like a very valuable thing to
unblock with this release.
– Ufuk
On Thu, Aug 1, 2019 at 11:02 AM Stephan Ewen wrote:
> Hi all!
>
> I would like to backport a minor chance from
+1
On Mon, Jul 29, 2019 at 11:06 AM Jeff Zhang wrote:
> +1 to remove it.
>
> Aljoscha Krettek 于2019年7月29日周一 下午5:01写道：
>
> > Hi,
> >
> > Because of recent problems in the dependencies of that module [1] I would
> > suggest that we remove it. If people are using it, they can use the one
> >
Ufuk Celebi created FLINK-12813:
---
Summary: Add Hadoop profile in building from source docs
Key: FLINK-12813
URL: https://issues.apache.org/jira/browse/FLINK-12813
Project: Flink
Issue Type
Ufuk Celebi created FLINK-12313:
---
Summary:
SynchronousCheckpointITCase.taskCachedThreadPoolAllowsForSynchronousCheckpoints
is unstable
Key: FLINK-12313
URL: https://issues.apache.org/jira/browse/FLINK-12313
Ufuk Celebi created FLINK-12060:
---
Summary: Unify change pom version scripts
Key: FLINK-12060
URL: https://issues.apache.org/jira/browse/FLINK-12060
Project: Flink
Issue Type: Bug
t; Theoretically it is even possible to generate the licensing files from said
> output, but haven't had time yet to look into whether this is truly possible.
>
> On 19.03.2019 07:15, Ufuk Celebi wrote:
>
> Hey Aljoscha,
>
> thanks for bringing this up. I think that we
Hey Aljoscha,
thanks for bringing this up. I think that we should either integrate
checks for this into our CI/CD environment (using existing tools) or
add a conditional check for this into flink-bot in case a pom.xml was
modified. Otherwise it will be easy to forget in the future.
– Ufuk
On
I like Shaoxuan's idea to keep this a static site first. We could then
iterate on this and make it a dynamic thing. Of course, if we have the
resources in the community to quickly start with a dynamic site, I'm
not apposed.
– Ufuk
On Wed, Mar 6, 2019 at 2:31 PM Robert Metzger wrote:
>
>
I really like this effort. I think the original plan for
"cancel-with-savepoint" was always to just be a workaround until we
arrived at a better solution as proposed here.
Regarding the FLIP, I agree with Elias comments. I think the number of
termination modes the FLIP introduces can be
e explicitly.
>
> On Thu, Feb 28, 2019 at 1:59 PM Ufuk Celebi wrote:
>
> > I fully agree with Aljoscha and Chesnay (although my recent PR
> > experience was still close to what Stanislav describes).
> >
> > @Robert: Do we have standard labels that we apply to tickets tha
I fully agree with Aljoscha and Chesnay (although my recent PR
experience was still close to what Stanislav describes).
@Robert: Do we have standard labels that we apply to tickets that
report a flaky test? I think this would be helpful to make sure that
we have a good overview of the state of
Ufuk Celebi created FLINK-11784:
---
Summary: KryoSerializerSnapshotTest occasionally fails on Travis
Key: FLINK-11784
URL: https://issues.apache.org/jira/browse/FLINK-11784
Project: Flink
Issue
;
> On Tue, Feb 26, 2019 at 7:37 AM jincheng sun
> wrote:
>
> > Thanks for bringing up this DISCUSS Ufuk!
> >
> > Makes sense. +1 for doing this.
> >
> > Best,
> > Jincheng
> >
> > Ufuk Celebi 于2019年2月25日周一 下午10:33写道：
> >
> &g
Ufuk Celebi created FLINK-11752:
---
Summary: Move flink-python to opt
Key: FLINK-11752
URL: https://issues.apache.org/jira/browse/FLINK-11752
Project: Flink
Issue Type: Improvement
Dear devs,
what are your thoughts about moving flink-python (batch API) to opt
instead of having it in lib? The streaming counter part
(flink-streaming-python) is only as part of opt.
I think we don't have many users of the Python batch API. I think this
will make the streaming/batch experience
+1 for Feb 22. Thanks for being the release manager.
– Ufuk
On Tue, Feb 12, 2019 at 7:00 PM Stephan Ewen wrote:
>
> +1 for doing a 1.8 release soon.
>
> Some of the Table API refactoring work is blocked on a release (assuming we
> want one release to deprecate some functions before dropping
+1 to release 1.6.4
On Tue, Feb 12, 2019 at 10:01 AM jincheng sun wrote:
>
> Hi Flink devs,
>
> It has been a long time since the release of 1.6.3 (December 23, 2018).
> There have been a lot of valuable bug fixes during this period.
> What do you think about releasing Flink 1.6.4 soon?
>
> We
+1
@Gordon: There has been no further review of the PR that Shuyi linked
(https://github.com/apache/flink/pull/7356). Do you plan to block
1.7.2 on this or rather not?
– Ufuk
On Fri, Feb 8, 2019 at 10:35 PM Thomas Weise wrote:
>
> +1
>
>
> On Fri, Feb 8, 2019 at 6:14 AM jincheng sun
> wrote:
e's an agreed upon release schedule in
>> the Flink community (I've not been following the dev@ list closely
>> recently).
>> I'll try to find somebody who knows a bit more about the recent Flink
>> community developments to put together a first draft for such a r
Ufuk Celebi created FLINK-11545:
---
Summary: Add option to manually set job ID in
StandaloneJobClusterEntryPoint
Key: FLINK-11545
URL: https://issues.apache.org/jira/browse/FLINK-11545
Project: Flink
Ufuk Celebi created FLINK-11546:
---
Summary: Add option to manually set job ID in CLI
Key: FLINK-11546
URL: https://issues.apache.org/jira/browse/FLINK-11546
Project: Flink
Issue Type: Sub-task
Ufuk Celebi created FLINK-11544:
---
Summary: Add option manually set job ID for job submissions via
REST API
Key: FLINK-11544
URL: https://issues.apache.org/jira/browse/FLINK-11544
Project: Flink
Ufuk Celebi created FLINK-11534:
---
Summary: Don't exit JVM after job termination with standalone job
Key: FLINK-11534
URL: https://issues.apache.org/jira/browse/FLINK-11534
Project: Flink
Issue
Ufuk Celebi created FLINK-11533:
---
Summary: Retrieve job class name from JAR manifest in
ClassPathJobGraphRetriever
Key: FLINK-11533
URL: https://issues.apache.org/jira/browse/FLINK-11533
Project: Flink
Ufuk Celebi created FLINK-11525:
---
Summary: Add option to manually set job ID
Key: FLINK-11525
URL: https://issues.apache.org/jira/browse/FLINK-11525
Project: Flink
Issue Type: New Feature
Hey devs,
I've been only following Flink dev loosely in the last couple of
months and could not find the following information:
What's the schedule for the next release? In particular, when is the
planned feature freeze and when is the planned release date?
I think this can be valuable
I'm late to this party but big +1. Great idea! I think this will help
to better represent the actual Flink community size and increase
interaction between the English and non-English speaking community.
:-)
On Mon, Jan 28, 2019 at 6:02 PM jincheng sun wrote:
>
> +1，I like the idea very much！
>
>
re there was
> consensus whether the contribution was welcome or not.
>
> Am Mo., 28. Jan. 2019 um 16:54 Uhr schrieb Ufuk Celebi :
>
> > I played around with the bot and it works pretty well. :-) @Robert:
> > Are there any plans to contribute the code for the bot to Apache
> &g
(1) I agree with Aljoscha's line of arguing here. A staleness bot is
quite the opposite of “sweeping things under the rug". A clear and
automated message about the state of a PR provides good value to
contributors, reviewers, and other people monitoring PRs. Asking
committers to proactively close
I played around with the bot and it works pretty well. :-) @Robert:
Are there any plans to contribute the code for the bot to Apache
(potentially in another repository)?
I like Fabians suggestions. Regarding the questions:
1) I would make that dependent on whether you expected the review
On Wed, Jan 23, 2019 at 11:01 AM Timo Walther wrote:
> I think what is more important than a big dist bundle is a helpful
> "Downloads" page where users can easily find available filesystems,
> connectors, metric repoters. Not everyone checks Maven central for
> available JAR files. I just saw
I like the idea of a leaner binary distribution. At the same time I
agree with Jamie that the current binary is quite convenient and
connection speeds should not be that big of a deal. Since the binary
distribution is one of the first entry points for users, I'd like to
keep it as user-friendly as
Hey Stephan and others,
thanks for the summary. I'm very excited about the outlined improvements. :-)
Separate branch vs. fork: I'm fine with either of the suggestions.
Depending on the expected strategy for merging the changes, expected
number of additional changes, etc., either one or the
Ufuk Celebi created FLINK-11402:
---
Summary: User code can fail with an UnsatisfiedLinkError in the
presence of multiple classloaders
Key: FLINK-11402
URL: https://issues.apache.org/jira/browse/FLINK-11402
Thanks Chesnay.
+1 to drop since we are not using them (flink-libraries is empty and
incubator-flink redirects to flink in GitHub).
– Ufuk
On Wed, Jan 16, 2019 at 10:38 AM Chesnay Schepler wrote:
>
> I've filed https://issues.apache.org/jira/browse/INFRA-17666.
>
> On 16.01.2019 10:32, Tzu-Li
+1 to drop.
I totally agree with your reasoning. I like that we tried to keep it,
but I don't think the maintenance overhead would be justified.
– Ufuk
On Wed, Jan 9, 2019 at 4:09 PM Till Rohrmann wrote:
>
> With https://issues.apache.org/jira/browse/FLINK-10571, we will remove the
> Storm
Ufuk Celebi created FLINK-11127:
---
Summary: Make metrics query service establish connection to
JobManager
Key: FLINK-11127
URL: https://issues.apache.org/jira/browse/FLINK-11127
Project: Flink
+1. This seems reasonable to me. Since the fixes are already in and
also part of other releases, the release overhead should be
manageable.
@Vino: I agree with your assessment.
@Qi: As Till mentioned, the official project guideline is to support
the last two minor releases, e.g. currently 1.7
Ufuk Celebi created FLINK-10971:
---
Summary: Dependency convergence issue when building
flink-s3-fs-presto
Key: FLINK-10971
URL: https://issues.apache.org/jira/browse/FLINK-10971
Project: Flink
Ufuk Celebi created FLINK-10948:
---
Summary: Add option to write out termination message with
application status
Key: FLINK-10948
URL: https://issues.apache.org/jira/browse/FLINK-10948
Project: Flink
Hey Thomas,
On Fri, Nov 9, 2018 at 6:07 PM Thomas Weise wrote:
> Is there a way to activate the predefined options via configuration / flink-
> conf.yaml? Or only programmatically, like in [4]? The difficulty with the
> programmatic route (assuming this works now), is that in my case the client
Ufuk Celebi created FLINK-10751:
---
Summary: Checkpoints should be retained when job reaches suspended
state
Key: FLINK-10751
URL: https://issues.apache.org/jira/browse/FLINK-10751
Project: Flink
1 - 100 of 787 matches
Mail list logo
