TisonKun created FLINK-13334:
Summary: Remove legacy implementation of slot sharing
Key: FLINK-13334
URL: https://issues.apache.org/jira/browse/FLINK-13334
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-13335:
Summary: Align the SQL DDL with FLIP-37
Key: FLINK-13335
URL: https://issues.apache.org/jira/browse/FLINK-13335
Project: Flink
Issue Type: Sub-task
Hi Zili,
Thank you for bring us this discussion.
My gut feeling is +1 for dropping it.
Usually it costs some time to deprecate a public (actually it's
`PublicEvolving`) API. Ideally it should be marked as `Deprecated` first.
Then it might be abandoned it in some later version.
I'm not sure how b
I did modify the .travis.yml do activate the unsafe-mapr-repo profile;
did I modified the wrong profile?...
On 19/07/2019 07:57, Jark Wu wrote:
It seems that it is introduced by this commit:
https://github.com/apache/flink/commit/5c36c650e6520d92191ce2da33f7dcae774319f6
Hi @Chesnay Schepler ,
Ah, I added it to the common options in the travis_manv_watchdog.sh .
On 19/07/2019 09:58, Chesnay Schepler wrote:
I did modify the .travis.yml do activate the unsafe-mapr-repo profile;
did I modified the wrong profile?...
On 19/07/2019 07:57, Jark Wu wrote:
It seems that it is introduced by
Zhu Zhu created FLINK-13336:
---
Summary: Remove the legacy batch fault tolerance page and redirect
it to the new task failure recovery page
Key: FLINK-13336
URL: https://issues.apache.org/jira/browse/FLINK-13336
In my experience a basic "official" (but optional) program description
would be very useful indeed (in order to ease the integration with other
frameworks).
Of course it should be extended and integrated with the REST services and
the Web UI (when defined) in order to be useful..
It ease to show t
XuPingyong created FLINK-13337:
--
Summary: Do not need to backup and restore streamEnv config in
BatchExecutor
Key: FLINK-13337
URL: https://issues.apache.org/jira/browse/FLINK-13337
Project: Flink
I think I found the issue; I forgot to update travis_controller.sh .
On 19/07/2019 10:02, Chesnay Schepler wrote:
Ah, I added it to the common options in the travis_manv_watchdog.sh .
On 19/07/2019 09:58, Chesnay Schepler wrote:
I did modify the .travis.yml do activate the unsafe-mapr-repo
pro
Hello,
the Flink PMC was a while ago informed about a security risk in our
build process, as we were accessing various maven repositories without
HTTPS. This issue was resolved in FLINK-12578 for 1.7 on-wards.
However, there is an ongoing issue with the MapR repository where you
may run into
Hi Biao,
Thanks for your reply.
For the "burden" part, inside PackagedProgram and ClusterClient
we currently contains branches handling whether the mainClass of
user job jar is subclass of Program. Any effort under client api
enhancement should be compatible with such codepaths unless we
drop it.
To Flavio, good point for the integration suggestion.
I think it should be considered in the "Flink client api enhancement"
discussion. But the outdated API should be deprecated somehow.
Flavio Pompermaier 于2019年7月19日周五 下午4:21写道：
> In my experience a basic "official" (but optional) program desc
Hi Flavio,
Thanks for your reply and share.
I agree with that an "official" program description
would be helpful as you described.
However, this thread mainly focuses on drop the stale
class Program.
For proposing a better program description from Flink
side, feel free to start a new thread on
+1 to remove directly the Program class (I think nobody use it and it's not
supported at all by REST services and UI).
Moreover it requires a lot of transitive dependencies while it should be a
very simple thing..
+1 to add this discussion to "Flink client api enhancement"
On Fri, Jul 19, 2019 at
HiGuys,
I want to contribute to ApacheFlink.Would you please give me the permission as
a contributor?
My JIRA ID is zhenggui.
best regards!
Hi,
There is no need for contribution permission anymore, see [1].
1.
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-JIRA-permissions-changed-Only-committers-can-assign-somebody-to-a-ticket-td30695.html
蒋正贵 于2019年7月19日周五 下午5:21写道：
> HiGuys,
>
> I want to contribute to
Hi,
As an addition, you can checkout
https://flink.apache.org/contributing/contribute-code.html
to see the contribution workflow.
Best,
tison.
Biao Liu 于2019年7月19日周五 下午5:32写道：
> Hi,
>
> There is no need for contribution permission anymore, see [1].
>
> 1.
>
> http://apache-flink-mailing-list-
Great! Thanks Chesnay for the quick fixing.
On Fri, 19 Jul 2019 at 16:40, Chesnay Schepler wrote:
> I think I found the issue; I forgot to update travis_controller.sh .
>
> On 19/07/2019 10:02, Chesnay Schepler wrote:
> > Ah, I added it to the common options in the travis_manv_watchdog.sh .
> >
I thought about this, but decided against it. I would hope that everybody
who's involved with the development in a way that they assign issues to
themselves is also active on this list.
Users who just report a bug should not just assign themselves.
If you disagree with me, feel free to forward the
Danny Chan created FLINK-13338:
--
Summary: Add sql conformance config interface in TableConfig
Key: FLINK-13338
URL: https://issues.apache.org/jira/browse/FLINK-13338
Project: Flink
Issue Type: B
Hi all!
Chesnay wrote:
> We haven't wiped the set of contributors yet. Not sure if there's an
> easy way to remove the permissions for all of them; someone from the PMC
> may have to bite the bullet and click 600 times in a row :)
I don't think there's an easy way for us.
People with "Contribut
that was the issue , thanks so much man!!
AU
On Thu, Jul 18, 2019 at 8:56 PM Caizhi Weng wrote:
> Hi Andres,
>
> `provided` of flink-streaming-java seems suspicious, can you
> remove it and see what happens?
>
> Andres Angel 于2019年7月19日周五 上午3:10写道：
>
> > Hello everyone,
> >
> > I'm using Intell
Hi all,
I agree with Aljoscha that trying to reflect the current status in the
bylaws, and then implementing changes one by one is a very involved task.
Unless there's somebody who's really eager to drive this, I would stick to
Becket's initiative to come up with Bylaws for Flink, even if this mean
Hi Jincheng,
Thanks for the comments. I replied on the wiki page. Just a brief summary,
the current bylaws do require some of the FLIPs to get PMC approval if
their impact is big enough. But it leaves majority of the technical
decisions to the committers who are supposed to be responsible for maki
Hey, Robert.
I will keep an eye on the overall progress and get started on the blog post
to make the community announcement. Are there (mid-term) plans to
translate/localize this website as well? It might be a point worth
mentioning in the blogpost.
Hats off to you and Daryl — this turned out ama
Hey,
I was wondering about the relation between the parallelism set by YARN in
Yarn properties file. Currently, as far as I know there is only one
execution of `writeYarnPropertiesFIle` method and it sets the parallelism
in the YARN properties to the number of workers * number of slots per
worker.
Xu Yang created FLINK-13339:
---
Summary: Add an implementation of pipeline's api
Key: FLINK-13339
URL: https://issues.apache.org/jira/browse/FLINK-13339
Project: Flink
Issue Type: Sub-task
DuBin created FLINK-13340:
-
Summary: Add more Kafka topic option of flink-connector-kafka
Key: FLINK-13340
URL: https://issues.apache.org/jira/browse/FLINK-13340
Project: Flink
Issue Type: Improvemen
The website is awesome! I really like its conciseness and yet fairly useful
information and functionalities. I cannot think of much to improve at the
moment. Just one thought, do we need an "others" category, just in case a
package does not fit into any of the current given categories?
Thanks Robe
[Sorry for the incomplete message. Clicked send by mistake...]
I agree with Marta that it might be good to have multi-language support as
a mid-term goal.
Jiangjie (Becket) Qin
On Sat, Jul 20, 2019 at 11:22 AM Becket Qin wrote:
> The website is awesome! I really like its conciseness and yet fa
Hi all,
As far as I know, currently, email notifications of Travis builds for
master branch are sent to the commit author when a build was just broken or
still is broken. And there is no email notifications for CRON builds.
Recently, we are suffering from compile errors for scala-2.12 and java-9
There are many reasons for jira, and one of the most important reasons is
that flink varies greatly from version to version. However, I agree that
you restrict some rights of developers, including the right to assign and
edit.
Robert Metzger 于2019年7月19日周五 下午10:58写道：
> Hi all!
>
> Chesnay wrote:
+1 ,Thanks jark for the proposal.
Best
Forward
Jark Wu 于2019年7月20日周六 下午12:14写道：
> Hi all,
>
> As far as I know, currently, email notifications of Travis builds for
> master branch are sent to the commit author when a build was just broken or
> still is broken. And there is no email notifications
33 matches
Mail list logo
