Great feature, I kinda like how the dialect / conformance is handled.
+1. also could you please update the FLIP-123 link and add a
summary/description row in the main page[1] please?
Thanks,
Rong
--
[1]
https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals
On Tue, Apr 14
Congratulations to all!!!
--
Rong
On Wed, Apr 1, 2020 at 2:27 PM Thomas Weise wrote:
> Congratulations!
>
>
> On Wed, Apr 1, 2020 at 9:31 AM Fabian Hueske wrote:
>
> > Congrats everyone!
> >
> > Cheers, Fabian
> >
> > Am Mi., 1. Apr. 2020 um 18:26 Uhr schrieb Yun Tang :
> >
> > > Congratulatio
Rong Rong created FLINK-16789:
-
Summary: Support JMX RMI via JMXConnectorServer
Key: FLINK-16789
URL: https://issues.apache.org/jira/browse/FLINK-16789
Project: Flink
Issue Type: New Feature
Thanks @Till for sharing the JIRA information.
I thought as well that this should not be an isolated case to our
situation. We would continue to follow up on the JIRA ticket.
Best,
Rong
On Fri, Mar 20, 2020 at 7:30 AM Till Rohrmann wrote:
> Hi Rong Rong,
>
> you are right that it JMX
am not
sure that would eventually happen.
--
Rong
On Fri, Mar 13, 2020 at 6:43 AM Aljoscha Krettek
wrote:
> Thanks for the update!
>
> On 13.03.20 13:47, Rong Rong wrote:
> > 1. I think we have finally pinpointed what the root cause to this issue
> is:
> > When partitio
Hi All,
Has anyone tried to manage production Flink applications through JMX remote
monitoring & management[1]?
We were experimenting to enable JMXRMI on Flink by default in production
and would like to share some of our thoughts:
** Is there any straightforward way to dynamically allocate JMXRMI
but somehow still want to avoid a certain amount of data loss. Most
of our analytics use cases falls into this category.
--
Rong
[1] https://issues.apache.org/jira/browse/KAFKA-6362
[2] https://github.com/apache/kafka/pull/4326
On Wed, Mar 11, 2020 at 10:16 AM Aljoscha Krettek
wrote:
>
Hi All,
I would like to bring back this discussion which I saw multiple times in
previous ML threads [1], but there seem to have no solution if
checkpointing is disabled.
All of these ML reported exceptions have one common pattern:
> *INFO* org.apache.kafka.clients.consumer.internals.AbstractCoo
nificant
> > >>>>>> portion is spent on polishing the language. If the blog does not
> > >>>> require
> > >>>>>> such formal and high quality languages, I believe it will make
> > >>> things a
> > >>>>>
+1 (binding)
--
Rong
On Fri, Mar 6, 2020 at 6:43 PM Peter Huang
wrote:
> Hi Kostas,
>
> Thanks for the effort of combing our needs with the long term goal of
> execution mode of Flink application.
> Looking forward to the feature in Flink
>
> +1 (non-binding) from my side
>
>
> Best Regards
> P
Big +1 on this. Some of these topics are not only for contributors, but
would also be super useful for advance users.
One topic I can think of in addition is: Security/Kerberos.
Echo on Both Seth's idea, we could have both wiki and PR submission:
As Robert mentioned - wiki submission would make th
Rong Rong created FLINK-16236:
-
Summary: Fix YARNSessionFIFOSecuredITCase not loading the correct
security context factory
Key: FLINK-16236
URL: https://issues.apache.org/jira/browse/FLINK-16236
Project
Congratulations Jingsong!!
Cheers,
Rong
On Fri, Feb 21, 2020 at 8:45 AM Bowen Li wrote:
> Congrats, Jingsong!
>
> On Fri, Feb 21, 2020 at 7:28 AM Till Rohrmann
> wrote:
>
>> Congratulations Jingsong!
>>
>> Cheers,
>> Till
>>
>> On Fri, Feb 21, 2020 at 4:03 PM Yun Gao wrote:
>>
>>> Congr
Rong Rong created FLINK-16224:
-
Summary: Refine Hadoop Delegation Token based testing framework
Key: FLINK-16224
URL: https://issues.apache.org/jira/browse/FLINK-16224
Project: Flink
Issue Type
t this is only a thought and still have many details to iron
out.
We would share the design doc soon, and we would love to hear more of your
ideas and looking forward to your feedbacks.
Thanks,
Rong
On Sun, Feb 16, 2020 at 7:02 PM Yang Wang wrote:
> Hi Rong Rong,
>
>
> Thanks for s
>
> Best,
> Aljoscha
>
> [1] https://issues.apache.org/jira/browse/FLINK-14317
>
> On 13.02.20 03:47, SHI Xiaogang wrote:
> > Hi Rong Rong,
> >
> > Thanks for the proposal. We are also suffering from some pains brought by
> > history server. To address them
+1 (binding)
On Fri, Feb 14, 2020 at 7:15 AM Zhijiang
wrote:
> +1 (binding), it is valuable to enhance the python API for supporting ML
> well.
>
> Best,
> Zhijiang
>
>
> --
> From:Dian Fu
> Send Time:2020 Feb. 14 (Fri.) 15:07
> To
Thanks for driving this initiative @Hequn Cheng .
Moving towards python based ML is definitely a huge win consider how large
the python-ML community is. a big +1 on my side!
Regarding the doc, I only left a few comments on the specific APIs. overall
the architecture looks very good!
Looking forwa
Hi All,
Recently we have been experimenting using Flink’s history server as a
centralized debugging service for completed streaming jobs.
Specifically, we dynamically generate links to access log files on the YARN
host; in the meantime, we use the Flink history server to show job graphs,
exceptio
can revisit this
> easily instead of blocking the improvement for users. What do you think?
>
> Best,
> Hequn
>
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Support-Python-ML-Pipeline-API-td37291.html
>
> On Sat, Feb 8, 2020 at 1:57 AM Rong Ro
CC @Xu Yang
Thanks for starting the discussion @Hequn Cheng and
sorry for joining the discussion late.
I've mainly helped merging the code in flink-ml-api and flink-ml-lib in the
past several months.
IMO the flink-ml-api are an extension on top of the table API and agree
that it should be treat
+1
--
Rong
On Wed, Jan 29, 2020 at 8:51 AM Ismaël Mejía wrote:
> +1 (non-binding)
>
> No more maintenance work for us Patrick! Just kidding :), it was mostly
> done by Patrick, all kudos to him.
> Just one question, we will be able to still be featured as an official
> docker image in this case
Rong Rong created FLINK-15561:
-
Summary: Improve Kerberos delegation token login
Key: FLINK-15561
URL: https://issues.apache.org/jira/browse/FLINK-15561
Project: Flink
Issue Type: Bug
Rong Rong created FLINK-15475:
-
Summary: Add isOutputTypeUsed() API to Transformation
Key: FLINK-15475
URL: https://issues.apache.org/jira/browse/FLINK-15475
Project: Flink
Issue Type
Congrats Zhu Zhu :-)
--
Rong
On Sat, Dec 14, 2019 at 4:47 AM tison wrote:
> Congratulations!:)
>
> Best,
> tison.
>
>
> OpenInx 于2019年12月14日周六 下午7:34写道：
>
> > Congrats Zhu Zhu!
> >
> > On Sat, Dec 14, 2019 at 2:38 PM Jeff Zhang wrote:
> >
> > > Congrats, Zhu Zhu!
> > >
> > > Paul Lam 于2019年1
Hi Leo,
Thanks for sharing the JIRA ticket and the idea of supporting multiple
Kafka topic in KafkaTableSource.
I've also commented on the JIRA ticket so sorry for joining the discussion
late.
My question was similar to @Jingsong's:
1. can you share some concrete examples on how this could benefi
Thanks @Tison for starting the discussion and sorry for joining so late.
Yes, I think this is a very good idea. we already tweak the flink-yarn
package internally to support something similar to what @Thomas mentioned:
to support registering a Jar that has already uploaded to some DFS
(needless to
Congratulations Jark!!!
On Fri, Nov 8, 2019 at 10:03 AM Xuefu Z wrote:
> Many congratulations, Jark!
>
> On Fri, Nov 8, 2019 at 2:31 AM wenlong.lwl
> wrote:
>
> > Congratulations Jark, well deserved!
> >
> >
> > Best,
> > Wenlong Lyu
> >
> > On Fri, 8 Nov 2019 at 18:22, tison wrote:
> >
> > >
Congratulations Becket!!
--
Rong
On Mon, Oct 28, 2019, 7:53 AM Jark Wu wrote:
> Congratulations Becket!
>
> Best,
> Jark
>
> On Mon, 28 Oct 2019 at 20:26, Benchao Li wrote:
>
> > Congratulations Becket.
> >
> > Dian Fu 于2019年10月28日周一 下午7:22写道：
> >
> > > Congrats, Becket.
> > >
> > > > 在 2019年
+1 (binding)
Thanks Timo for driving this.
--
Rong
On Mon, Oct 21, 2019 at 8:19 AM wrote:
> +1 (binding)
>
> Best,
> Xingcan
>
> -Original Message-
> From: jincheng sun
> Sent: Monday, October 21, 2019 5:04
> To: dev
> Subject: Re: [VOTE] FLIP-65: New type inference for Table API UDF
Hi Yijie,
I also agree with Jark on separating the Catalog part into another FLIP.
With FLIP-27[1] also in the air, it is also probably great to split and
unblock the sink implementation contribution.
I would suggest either putting in a detail implementation plan section in
the doc, or (maybe too
Hi Gyula,
Sorry for the late reply. I think it is definitely a challenge in terms of
log visibility.
However, for your requirement I think you can customize your Flink job by
utilizing a customized log formatter/encoder (e.g. log4j.properties or
logback.xml) and a suitable logger implementation.
> >
> > Thanks,
> > Thomas
> >
> > On Fri, Sep 27, 2019 at 9:29 AM Rong Rong wrote:
> >
> > > +1 on to state with one recommendation method in the wiki.
> > > I haven't encountered this often, so I do not have a preference
> regarding
inding? Committer votes are
> binding :-)
>
> Thanks,
> Timo
>
> On 29.09.19 02:17, Rong Rong wrote:
> > +1 (non-binding). Thanks for the effort and leading the discussions @Jark
> >
> > --
> > Rong
> >
> > On Thu, Sep 26, 2019 at 7:36 PM Ji
+1 (non-binding). Thanks for the effort and leading the discussions @Jark
--
Rong
On Thu, Sep 26, 2019 at 7:36 PM JingsongLee
wrote:
> +1 non-binding
> (nit: Add a road map?)
>
> Best,
> Jingsong Lee
>
>
> --
> From:Kurt Young
> S
+1 on to state with one recommendation method in the wiki.
I haven't encountered this often, so I do not have a preference regarding
which way to go (Gitbox or Github). However, I've experienced some
different issues on both Github and Gitbox when setting up new committer
credentials.
If possible,
ed a FLIP that describes the current design of the Pulsar
> connector:
>
>
> https://docs.google.com/document/d/1rES79eKhkJxrRfQp1b3u8LB2aPaq-6JaDHDPJIA8kMY/edit#
>
> Please take a look and let me know what you think.
>
> Thanks,
> Yijie
>
> On Sat, Sep 14, 20
Hi All,
Sorry for joining the discussion late and thanks Yijie & Sijie for driving
the discussion.
I also think the Pulsar connector would be a very valuable addition to
Flink. I can also help out a bit on the review side :-)
Regarding the timeline, I also share concerns with Becket on the
relati
Congratulations Zili!
--
Rong
On Wed, Sep 11, 2019 at 6:26 PM Hequn Cheng wrote:
> Congratulations!
>
> Best, Hequn
>
> On Thu, Sep 12, 2019 at 9:24 AM Jark Wu wrote:
>
>> Congratulations Zili!
>>
>> Best,
>> Jark
>>
>> On Wed, 11 Sep 2019 at 23:06, wrote:
>>
>> > Congratulations, Zili.
>> >
Thanks for putting together the proposal @Timo and sorry for joining the
discussion thread late.
I also share the same thought with Fabian on the ease-of-use front. However
I was wondering if we need to start the expression design with them?
One thing I can think of is: is it possible to support "
Congratulations Andrey!
On Wed, Aug 14, 2019 at 10:14 PM chaojianok wrote:
> Congratulations Andrey!
> At 2019-08-14 21:26:37, "Till Rohrmann" wrote:
> >Hi everyone,
> >
> >I'm very happy to announce that Andrey Zagrebin accepted the offer of the
> >Flink PMC to become a committer of the Flink
Congratulations Hequn, well deserved!
--
Rong
On Wed, Aug 7, 2019 at 8:30 AM wrote:
> Congratulations, Hequn!
>
>
>
> *From:* Xintong Song
> *Sent:* Wednesday, August 07, 2019 10:41 AM
> *To:* dev@flink.apache.org
> *Cc:* user
> *Subject:* Re: [ANNOUNCE] Hequn becomes a Flink committer
>
>
>
We've also experienced some issues with our internal JFrog artifactory. I
am suspecting some sort of mirroring problem but somehow it only occur to
the mapr-fs module.
So +1 to remove.
On Mon, Jul 29, 2019 at 12:47 PM Stephan Ewen wrote:
> It should be fairly straightforward to rewrite the code
Hi Shuyi,
I think there were some discussions in the mailing list [1,2] and JIRA
tickets [3,4] that might be related.
Since the table-blink planner doesn't produce such error, I think this
problem is valid and should be fixed.
Thanks,
Rong
[1]
http://apache-flink-user-mailing-list-archive.233605
Rong Rong created FLINK-13389:
-
Summary: Setting DataStream return type breaks some type
conversion between Table and DataStream
Key: FLINK-13389
URL: https://issues.apache.org/jira/browse/FLINK-13389
Congratulations Kurt!!
--
Rong
On Tue, Jul 23, 2019 at 7:31 AM zhijiang
wrote:
> Congrats Kurt!
>
> Best,
> Zhijiang
> --
> From:Till Rohrmann
> Send Time:2019年7月23日(星期二) 21:08
> To:dev
> Subject:Re: [ANNOUNCE] Kete Young is now
Congratulations Becket!
--
Rong
On Thu, Jul 18, 2019 at 7:05 AM Xingcan Cui wrote:
> Congrats Becket!
>
> Best,
> Xingcan
>
> On Thu, Jul 18, 2019, 07:17 Dian Fu wrote:
>
> > Congrats Becket!
> >
> > > 在 2019年7月18日，下午6:42，Danny Chan 写道：
> > >
> > >> Congratulations!
> > >
> > > Best,
> > > Da
see when
"PushProjectIntoTableSourceScanRule" gets invoked.
--
Rong
--
Rong
On Fri, Jul 12, 2019 at 8:33 PM Caizhi Weng wrote:
> Hi Rong,
>
> Thanks for your explanation. What I'm wondering when implementing this
> interface is that, will `projectFields` be called twice
Hi Caizhi,
from my understanding, the "ProjectableTableSource" interface is used for
something like predicator push-down scenarios:
where your produced output should be the same as how your SELECT statement
requires.
For example, in the case of:
SourceSchema: {a: Int, b: Double, c: String, d: Lon
gt;>> Best,
>>> >>>> Xingcan
>>> >>>>
>>> >>>> On Jul 11, 2019, at 1:08 PM, Shuyi Chen wrote:
>>> >>>>
>>> >>>> Congratulations, Rong!
>>> >>>>
>>> >>>>
Hi Aljoscha,
Sorry for the late reply, I think the solution makes sense. Using the NULL
return value to mark a message is corrupted is not a valid way since NULL
value has semantic meaning in not just Kafka but also in a lot of other
contexts.
I was wondering if we can have a more meaningful inte
Hi Fan, John,
The flink internal link[1] seems to be not updated in the last years.
I found out some higher level pages in the official documentation here[2]
however they are still very limited.
Is there any other well maintained, internal documentations for
contributors?
I think it might be a go
+1 for the deletion.
Also I think it also might be a good idea to update the roadmap for the
plan of removal/development since we've reached the consensus on FLIP-39.
Thanks,
Rong
On Wed, May 22, 2019 at 8:26 AM Shaoxuan Wang wrote:
> Hi Chesnay,
> Yes, you are right. There is not any active
's table API approach), I will follow up on the discussion
thread and the PR on FLIP-23 with you and Boris :-)
--
Rong
On Mon, May 6, 2019 at 3:30 AM Shaoxuan Wang wrote:
>
> Thanks for the feedback, Rong and Flavio.
>
> @Rong Rong
> > There's another thread regard
scalanlp/breeze
[2] https://spark.apache.org/docs/latest/ml-guide.html
On Tue, Apr 30, 2019 at 2:33 AM Robert Metzger wrote:
> Hey all,
>
> I'm wondering if somebody on the list can take a look at the PR from
> FLIP-23: https://github.com/apache/flink/pull/7446
>
>
> On Mon, Oct 1,
Hi Shaoxuan/Weihua,
Thanks for the proposal and driving the effort.
I also replied to the original discussion thread, and still a +1 on moving
towards the ski-learn model.
I just left a few comments on the API details and some general questions.
Please kindly take a look.
There's another thread r
Hi Zhipeng,
Please see my explanation below:
>From the default EventTimeTrigger source code, I found that only onElement
> method (will judge the watermark) and onEventTime method only have a chance
> to trigger TriggerResult.FIRE;
> Therefore, the default EventTimeTrigger is assumed and must be
Thanks Artsem for looking into this problem and Thanks Dawid for bringing
up the discussion on FLIP-30.
We've observe similar scenarios when we also would like to reuse the schema
registry of both Kafka stream as well as the raw ingested kafka messages in
datalake.
FYI another more catalog-oriente
Hi All,
Sorry for joining the discussion late. Thanks Piotrek for initiating this
effort.
I recall reporting a very similar bug years ago[1] that was not easily
solvable at the time, so +1 on this feature goes beyond just FileSystem :-)
I think this would definitely be beneficial as a useful way
Congrats! Thanks Aljoscha for being the release manager and all for making
the release possible.
--
Rong
On Wed, Apr 10, 2019 at 4:23 AM Stefan Richter
wrote:
> Congrats and thanks to Aljoscha for managing the release!
>
> Best,
> Stefan
>
> > On 10. Apr 2019, at 13:01, Biao Liu wrote:
> >
>
+1 (non-binding)
* Verified checksums and GPG files matches release files
* Verified that the source archives do not contain any binaries
* Built the source with Maven to ensure all source files have Apache headers
* Checked that all POM files point to the same version
* `mvn clean verify` against
Hi @Aljoscha,
Based on the previous commit [1] that adds the random port selection code,
it seems like the important part is to unset whatever 'rest.port' setting
previously done. I don't think the current way of setting the BIND_PORT
actually overrides any existing PORT setting. However, I wasn't
Thanks @Timo for starting this effort and preparing the document :-)
I took a pass and left some comments. I also very much like the idea of the
DataType and LogicalType separation.
As explained in the doc, we've also been looking into ways to improve the
type system so a huge +1 on our side.
One
take a look at the initial design document here [1]. Any
comments or suggestions are highly appreciated!
Thanks,
Rong
--
[1]
https://docs.google.com/document/d/1CvjPJl1Fm1PCpsuuZ4Qc-p_iUzUosBePX_rWNUt8lRw/edit#
On Thu, Feb 28, 2019 at 2:24 PM Rong Rong wrote:
> Hi Kurt,
>
> Thanks for
e generic solution. Thanks!
> Tao Yang
>
>
> ------
> 发件人：Rong Rong
> 发送时间：2018年12月19日(星期三) 03:06
> 收件人：dev
> 主 题：Re: [DISCUSS] Flink Kerberos Improvement
>
> Hi Shuyi,
>
> Yes. I think the impersonation is a very
; Cheers,
> Till
>
> On Wed, Mar 13, 2019 at 5:42 PM Rong Rong wrote:
>
>> Thanks for raising the concern @shuyi and the explanation @konstantin.
>>
>> Upon glancing on the Flink document, it seems like user have full control
>> on the timeout behavior [1]. But u
Thanks for sharing the initiative of improving Java side Table expression
DSL.
I agree as in the doc stated that Java DSL was always a "3rd class citizen"
and we've run into many hand holding scenarios with our Flink developers
trying to get the Stringify syntax working.
Overall I am a +1 on this,
Rong Rong created FLINK-11936:
-
Summary: Remove AuxiliaryConverter pull-in from calcite and fix
auxiliary converter issue.
Key: FLINK-11936
URL: https://issues.apache.org/jira/browse/FLINK-11936
Project
Rong Rong created FLINK-11935:
-
Summary: Remove DateTimeUtils pull-in and fix datetime casting
problem
Key: FLINK-11935
URL: https://issues.apache.org/jira/browse/FLINK-11935
Project: Flink
Thanks for raising the concern @shuyi and the explanation @konstantin.
Upon glancing on the Flink document, it seems like user have full control
on the timeout behavior [1]. But unlike AsyncWaitOperator, it is not
straightforward to access the internal state of the operator to, for
example, put th
Rong Rong created FLINK-11909:
-
Summary: Provide default failure/timeout handling strategy for
AsyncIO functions
Key: FLINK-11909
URL: https://issues.apache.org/jira/browse/FLINK-11909
Project: Flink
operator internally when we
> decide to add new APIs, which you have covered a lot in your proposal.
> Actually, the approaches you proposed looks good to me, take it step by
> step is a more practical way.
>
> Best,
> Kurt
>
>
> On Fri, Feb 22, 2019 at 2:58 AM Rong Rong wro
Rong
On Thu, Feb 21, 2019 at 8:50 AM Stephan Ewen wrote:
> Hi Rong Rong!
>
> I would add the security / kerberos threads to the roadmap. They seem to
> be advanced enough in the discussions so that there is clarity what will
> come.
>
> For the window operator with slicing, I
ows whose window size
> can't be divided by step, such as 10 seconds window and slide with 3
> seconds?
>
> Best,
> Kurt
>
>
> On Wed, Jan 30, 2019 at 2:12 AM Fabian Hueske wrote:
>
> > Thank you Rong!
> > The performance of sliding windows is an
t;>> Because it is easier to update the roadmap on wiki compared to on flink web
>>> site. And I guess we may need to update the roadmap very often at the
>>> beginning as there's so many discussions and proposals in community
>>> recently. We can move it into fli
-list-archive.1008284.n3.nabble.com/DISCUSS-Flink-security-improvements-td21068.html
>
> On Tue, Dec 18, 2018 at 8:06 PM Rong Rong wrote:
>
> > Hi Shuyi,
> >
> > Yes. I think the impersonation is a very much valid question! This can
> > actually be considered as
Thanks Stephan for the great proposal.
This would not only be beneficial for new users but also for contributors
to keep track on all upcoming features.
I think that better window operator support can also be separately group
into its own category, as they affects both future DataStream API and b
Rong Rong created FLINK-11589:
-
Summary: Introduce service provider pattern for user to
dynamically load SecurityFactory classes
Key: FLINK-11589
URL: https://issues.apache.org/jira/browse/FLINK-11589
Hi all,
Thanks @Jark for creating the translation terminology document! I think the
idea of keeping some of the terminologies untranslated and keeping such
document in place is absolutely good.
I actually share the same concern with @Shaoxuan regarding the discrepancy
getting larger. The dilemma i
Rong Rong created FLINK-11569:
-
Summary: Row type does not serialize in to readable format when
invoke "toString" method
Key: FLINK-11569
URL: https://issues.apache.org/jira/browse/FLINK-11569
+1. Thanks for the proposal @Jark.
I think utilizing review-bot will definitely be a good plus.
I remember @Robert mentioned that there was an auto checklist
functionality, maybe we can utilize that to flag/tag a specific PR is ready
for documentation parity review?
I would also like to follow up
Rong Rong created FLINK-11456:
-
Summary: Improve window operator with sliding window assigners
Key: FLINK-11456
URL: https://issues.apache.org/jira/browse/FLINK-11456
Project: Flink
Issue Type
On Wed, Dec 5, 2018 at 6:17 PM Rong Rong wrote:
> Hi all,
>
> Various discussion in the mailing list & JIRA tickets [2] had been brought
> up in the past regarding the windowing operation performance. As we
> experiment internally with some of our extreme use cases, we found
Rong Rong created FLINK-11455:
-
Summary: Support evictor operations on slicing and merging
operators
Key: FLINK-11455
URL: https://issues.apache.org/jira/browse/FLINK-11455
Project: Flink
Issue
Rong Rong created FLINK-11454:
-
Summary: Support MergedStream operation
Key: FLINK-11454
URL: https://issues.apache.org/jira/browse/FLINK-11454
Project: Flink
Issue Type: Sub-task
Rong Rong created FLINK-11453:
-
Summary: Support SliceWindow with forwardable pane info
Key: FLINK-11453
URL: https://issues.apache.org/jira/browse/FLINK-11453
Project: Flink
Issue Type: Sub
Rong Rong created FLINK-11276:
-
Summary: Slicing Window Optimization
Key: FLINK-11276
URL: https://issues.apache.org/jira/browse/FLINK-11276
Project: Flink
Issue Type: New Feature
Rong Rong created FLINK-11271:
-
Summary: Improve Kerberos Credential Distribution
Key: FLINK-11271
URL: https://issues.apache.org/jira/browse/FLINK-11271
Project: Flink
Issue Type: Improvement
n invoke Flink client to deploy the job. Thanks a lot.
>
> Shuyi
>
> [1]
>
> https://docs.google.com/document/d/10V7LiNlUJKeKZ58mkR7oVv1t6BrC6TZi3FGf2Dm6-i8/edit
>
> On Mon, Dec 17, 2018 at 5:49 PM Rong Rong wrote:
>
> > Hi All,
> >
> > We have been exper
Hi All,
We have been experimenting integration of Kerberos with Flink in our Corp
environment and found out some limitations on the current Flink-Kerberos
security mechanism running with Apache YARN.
Based on the Hadoop Kerberos security guide [1]. Apparently there are only
a subset of the sugges
Thanks for the summary effort @shuyi. Sorry for jumping in the discussion
so late.
As of the scope of MVP, I think we might want to consider adding "table
update mode" problem to it. I agree with @timo that might not be easily
changed in the future if the flags has to be part of the schema/column
Rong Rong created FLINK-11088:
-
Summary: Improve Kerberos Authentication using Keytab in YARN
proxy user mode
Key: FLINK-11088
URL: https://issues.apache.org/jira/browse/FLINK-11088
Project: Flink
Hi all,
Various discussion in the mailing list & JIRA tickets [2] had been brought
up in the past regarding the windowing operation performance. As we
experiment internally with some of our extreme use cases, we found out that
using a slice-based implementation can optimize Flink's windowing mecha
Rong Rong created FLINK-11006:
-
Summary: Update Calcite dependency to 1.18
Key: FLINK-11006
URL: https://issues.apache.org/jira/browse/FLINK-11006
Project: Flink
Issue Type: Improvement
Hi Jincheng,
Thank you for the proposal! I think being able to define a process /
co-process function in table API definitely opens up a whole new level of
applications using a unified API.
In addition, as Tzu-Li and Hequn have mentioned, the benefit of
optimization layer of Table API will alread
+1. Thanks for putting the proposal together Shuyi.
DDL has been brought up in a couple of times previously [1,2]. Utilizing
DDL will definitely be a great extension to the current Flink SQL to
systematically support some of the previously brought up features such as
[3]. And it will also be benef
Hi Xuefu,
Thanks for putting together the overview. I would like to add some more on
top of Timo's comments.
1,2. I agree with Timo that a proper catalog support should also address
the metadata compatibility issues. I was actually wondering if you are
referring to something like utilizing table s
easy to do without
> the need for API changes.
>
> Piotrek
>
> On 1 Oct 2018, at 17:48, Rong Rong wrote:
>
> Hi Piotrek,
>
> Thanks for the quick response. To follow up with the questions:
> Re 1). Yes it is causing network I/O issues on Kafka itself.
>
> Re
Hi Timo,
Thanks for putting together the proposal!
I really love the idea to combining solution for historic and recent data
and left some suggestions on that part.
Regarding the table type, e.g. for kafka streams, I agree with @hequn's
idea that it should be pretty much inferable from the SQL co
Thanks for the contribution Boris!! I've been playing around with the basic
model for a while back and loved it.
+1 and really looking forward to having the feature merging back to Flink
ML.
--
Rong
On Mon, Oct 1, 2018 at 7:55 AM Fabian Hueske wrote:
> Hi everybody,
>
> The question of how to s
1 - 100 of 160 matches
Mail list logo
