Congrats Thomas!
Best,
Kurt
On Wed, Feb 13, 2019 at 10:02 AM Shaoxuan Wang wrote:
> Congratulations, Thomas!
>
> On Tue, Feb 12, 2019 at 5:59 PM Fabian Hueske wrote:
>
>> Hi everyone,
>>
>> On behalf of the Flink PMC I am happy to announce Thomas Weise as a new
>> member of the Apache Flink P
> do them a favor. Legal wise, my hunch is that it is probably OK for
> >>> someone
> >>>> to just build the jars and docs, host it somewhere for convenience.
> But
> >>> it
> >>>> should be clear that this is just for convenience purpose in
Big +1 on this, it will indeed help Chinese speaking users a lot.
fudian.fd 于2019年1月24日 周四20:18写道：
> +1. I noticed that many folks from China are requesting the JIRA
> permission in the past year. It reflects that more and more developers from
> China are using Flink. A Chinese oriented mailing l
-pi` if there are interested.
> I would not invest time into setting up a docs infrastructure.
>
> Regards,
> Timo
>
> Am 23.01.19 um 08:56 schrieb Kurt Young:
> > Thanks @Stephan for this exciting announcement!
> >
> > >From my point of view, i would prefer to
> 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
Hi Elias,
For your question 2: this is doable, i think it will be resolved in future
version of Flink.
Best,
Kurt
On Tue, Jan 15, 2019 at 10:35 PM Elias Saalmann <
es45g...@studserv.uni-leipzig.de> wrote:
> Hi there,
>
> I'm working on the Gradoop project at the University of Leipzig (
> https
Hi Driesprong,
Glad to hear that you're interested with blink's codes. Actually, blink
only has one branch by itself, so either a separated repo or a flink's
branch works for blink's code share.
Best,
Kurt
On Tue, Jan 22, 2019 at 2:30 PM Driesprong, Fokko
wrote:
> Great news Stephan!
>
> Why
+1 to the bot, but -1 to the automatically closing PR behavior.
Can we just use the bolt to detect and tag the PR with stale flag and leave
the decision whether to close the PR to the author?
Best,
Kurt
On Sun, Jan 13, 2019 at 11:49 PM Kostas Kloudas
wrote:
> +1 to try the bot.
>
> It may, at
Sounds great, thanks for the effort, Shuyi.
Best,
Kurt
On Wed, Dec 12, 2018 at 5:14 PM Shuyi Chen wrote:
> Hi all,
>
> I summarize the MVP based on the features that we agreed upon. For table
> update mode and custom watermark strategy and ts extractor, I found there
> are some discussions, so
Hi all,
Really excited to see this discussion really happens, I also want to share
my two cents here.
Lets first focus on this question: “What Flink API Stack Should be for a
Unified Engine".
There are multiply ways to judge whether an engine is unified or not. From
user's perspective, as long as
d long process. We
> > should be able to
> > regard it as a "technical debt", and if it does not change it, it will
> > also affect the decision-making of other issues.
> >
> > Thanks, vino.
> >
> > Kurt Young 于2018年11月27日周二 下午7:34写道：
> >
>
Hi Timo,
Thanks for writing up the document. I'm +1 for reorganizing the module
structure and make table scala free. But I have
a little concern abount the timing. Is it more appropriate to get this done
when Flink decide to bump to next big version, like 2.x.
It's true you can keep all the class'
Kurt Young created FLINK-7987:
-
Summary: Use RexBuilder when converting Expression to RexNode
Key: FLINK-7987
URL: https://issues.apache.org/jira/browse/FLINK-7987
Project: Flink
Issue Type
Congrats and welcome on board!
Best,
Kurt
On Wed, Nov 1, 2017 at 8:15 PM, Hai Zhou wrote:
> Congratulations!
>
> On 1. Nov 2017, at 10:13, Shaoxuan Wang wrote:
>
> Congratulations!
>
> On Wed, Nov 1, 2017 at 4:36 PM, Till Rohrmann
> wrote:
>
> Congrats and welcome on board :-)
>
> On Wed, Nov
Kurt Young created FLINK-7959:
-
Summary: Split CodeGenerator into CodeGeneratorContext and
ExprCodeGenerator
Key: FLINK-7959
URL: https://issues.apache.org/jira/browse/FLINK-7959
Project: Flink
+1 for droppint Java 7, we have been using Java 8 for more than one year in
Alibaba and everything work fine.
Best,
Kurt
On Thu, Jul 13, 2017 at 2:53 AM, Bowen Li wrote:
> +1 for dropping Java 7
>
> On Wed, Jul 12, 2017 at 9:04 AM, Gyula Fóra wrote:
>
> > +1 for dropping 1.7 from me as well.
>
Kurt Young created FLINK-7161:
-
Summary: Fix misusage of Double.MIN_VALUE and Float.MIN_VALUE
Key: FLINK-7161
URL: https://issues.apache.org/jira/browse/FLINK-7161
Project: Flink
Issue Type: Bug
Hi,
Ufuk had write up an excellent document about Netty's memory allocation [1]
inside Flink, and i want to add one more note after running some large
scale jobs.
The only inaccurate thing about [1] is how much memory will
LengthFieldBasedFrameDecoder
use. From our observations, it will cost at m
Hi Flavio,
I have also fix the issue in 1.2 branch, but the next release will be 1.2.2
Best,
Kurt
On Fri, Apr 28, 2017 at 11:01 PM, Ted Yu wrote:
> Flavio:
> Have you seen this (w.r.t. 1.2.1) ?
>
> http://search-hadoop.com/m/Flink/VkLeQejxLg24Lk0D1?subj=+
> RESULT+VOTE+Release+Apache+Flink+1+2
Kurt Young created FLINK-6398:
-
Summary: RowSerializer's duplicate should always return a new
instance
Key: FLINK-6398
URL: https://issues.apache.org/jira/browse/FLINK-6398
Project: Flink
Kurt Young created FLINK-6309:
-
Summary: Memory consumer weights should be calculated in job
vertex level
Key: FLINK-6309
URL: https://issues.apache.org/jira/browse/FLINK-6309
Project: Flink
Kurt Young created FLINK-6154:
-
Summary: Refine code reusing between logical and physical operators
Key: FLINK-6154
URL: https://issues.apache.org/jira/browse/FLINK-6154
Project: Flink
Issue
Kurt Young created FLINK-6150:
-
Summary: change DataSetCost to FlinkRelOptCost
Key: FLINK-6150
URL: https://issues.apache.org/jira/browse/FLINK-6150
Project: Flink
Issue Type: Sub-task
Kurt Young created FLINK-6149:
-
Summary: add additional flink logical relation nodes
Key: FLINK-6149
URL: https://issues.apache.org/jira/browse/FLINK-6149
Project: Flink
Issue Type: Sub-task
Kurt Young created FLINK-6066:
-
Summary: Separate logical and physical RelNode layer in Flink
Key: FLINK-6066
URL: https://issues.apache.org/jira/browse/FLINK-6066
Project: Flink
Issue Type: Sub
+1 to provide a unified code style for both java and scala.
-1 to adjust all the existing code to the new style in one step. The code's
history contains very helpful information which can help
develops to understand why these codes are added, which jira is related.
This information is too valuable
Congratulations Stefan!
Best,
Kurt
On Mon, Feb 13, 2017 at 3:42 AM, Kostas Kloudas wrote:
> Congratulations Stefan!
>
> Kostas
>
> > On Feb 12, 2017, at 7:17 PM, Chen Qin wrote:
> >
> > Congratulations!
> >
> > Chen
> >
> >> On Feb 10, 2017, at 02:00, Ufuk Celebi wrote:
> >>
> >> Hey everyon
Kurt Young created FLINK-5727:
-
Summary: Unify some API of batch and stream TableEnvironment
Key: FLINK-5727
URL: https://issues.apache.org/jira/browse/FLINK-5727
Project: Flink
Issue Type
have a query on a Table which was derived from at
> DataSet (no stats) which is joined with some external tables with stats.
> - Should we control the parallelism of operators based on cardinality
> information?
>
>
> Best, Fabian
>
> 2017-01-10 15:22 GMT+01:00 Kurt Young :
&
Kurt Young created FLINK-5570:
-
Summary: Support register external catalog to table environment
Key: FLINK-5570
URL: https://issues.apache.org/jira/browse/FLINK-5570
Project: Flink
Issue Type
Kurt Young created FLINK-5569:
-
Summary: Migrate current table registration to in-memory catalog
Key: FLINK-5569
URL: https://issues.apache.org/jira/browse/FLINK-5569
Project: Flink
Issue Type
Kurt Young created FLINK-5568:
-
Summary: Introduce interface for catalog, and provide an in-memory
implementation
Key: FLINK-5568
URL: https://issues.apache.org/jira/browse/FLINK-5568
Project: Flink
Kurt Young created FLINK-5567:
-
Summary: Introduce and migrate current table statistics to
FlinkStatistics
Key: FLINK-5567
URL: https://issues.apache.org/jira/browse/FLINK-5567
Project: Flink
Kurt Young created FLINK-5566:
-
Summary: Introduce structure to hold table and column level
statistics
Key: FLINK-5566
URL: https://issues.apache.org/jira/browse/FLINK-5566
Project: Flink
Issue
Kurt Young created FLINK-5565:
-
Summary: Improve flink cost model framework
Key: FLINK-5565
URL: https://issues.apache.org/jira/browse/FLINK-5565
Project: Flink
Issue Type: Improvement
Kurt Young created FLINK-5452:
-
Summary: Make table unit tests pass under cluster mode
Key: FLINK-5452
URL: https://issues.apache.org/jira/browse/FLINK-5452
Project: Flink
Issue Type
Kurt Young created FLINK-5435:
-
Summary: Cleanup the rules introduced by FLINK-5144 when calcite
releases 1.12
Key: FLINK-5435
URL: https://issues.apache.org/jira/browse/FLINK-5435
Project: Flink
Hi,
Currently flink already uses cost-based optimizer, but due to the reason
we didn’t have accurate statistics and the simple cost model, we actually
don't gain much from this framework. I proposed some improvements in the
following document and some rough implementation plan:
https://docs.googl
Kurt Young created FLINK-5315:
-
Summary: Support distinct aggregations in table api
Key: FLINK-5315
URL: https://issues.apache.org/jira/browse/FLINK-5315
Project: Flink
Issue Type: New Feature
Kurt Young created FLINK-5314:
-
Summary: Add tpch query explain test
Key: FLINK-5314
URL: https://issues.apache.org/jira/browse/FLINK-5314
Project: Flink
Issue Type: Sub-task
Kurt Young created FLINK-5313:
-
Summary: Supporting all tpch queries
Key: FLINK-5313
URL: https://issues.apache.org/jira/browse/FLINK-5313
Project: Flink
Issue Type: Improvement
Kurt Young created FLINK-5266:
-
Summary: Eagerly project unused fields when selecting aggregation
fields
Key: FLINK-5266
URL: https://issues.apache.org/jira/browse/FLINK-5266
Project: Flink
Kurt Young created FLINK-5257:
-
Summary: Display optimized logical plan when explaining table
Key: FLINK-5257
URL: https://issues.apache.org/jira/browse/FLINK-5257
Project: Flink
Issue Type
Kurt Young created FLINK-5251:
-
Summary: Decouple StreamTableSourceScan with TableSourceTable
Key: FLINK-5251
URL: https://issues.apache.org/jira/browse/FLINK-5251
Project: Flink
Issue Type
Kurt Young created FLINK-5185:
-
Summary: Decouple BatchTableSourceScan with TableSourceTable
Key: FLINK-5185
URL: https://issues.apache.org/jira/browse/FLINK-5185
Project: Flink
Issue Type
Kurt Young created FLINK-4839:
-
Summary: JobManager handle TaskManager's slot offering
Key: FLINK-4839
URL: https://issues.apache.org/jira/browse/FLINK-4839
Project: Flink
Issue Type: Sub
Kurt Young created FLINK-4807:
-
Summary: ResourceManager clean up JobManager's registration
Key: FLINK-4807
URL: https://issues.apache.org/jira/browse/FLINK-4807
Project: Flink
Issue Type
Kurt Young created FLINK-4806:
-
Summary: ResourceManager stop listening JobManager's leader address
Key: FLINK-4806
URL: https://issues.apache.org/jira/browse/FLINK-4806
Project: Flink
Kurt Young created FLINK-4735:
-
Summary: Migrate some job execution related akka messages to rpc
calls
Key: FLINK-4735
URL: https://issues.apache.org/jira/browse/FLINK-4735
Project: Flink
Issue
Kurt Young created FLINK-4690:
-
Summary: Replace SlotAllocationFuture with flink's own future
Key: FLINK-4690
URL: https://issues.apache.org/jira/browse/FLINK-4690
Project: Flink
Issue Type
Kurt Young created FLINK-4689:
-
Summary: Implement a simple slot provider for the new job manager
Key: FLINK-4689
URL: https://issues.apache.org/jira/browse/FLINK-4689
Project: Flink
Issue Type
Kurt Young created FLINK-4657:
-
Summary: Implement HighAvailabilityServices based on zookeeper
Key: FLINK-4657
URL: https://issues.apache.org/jira/browse/FLINK-4657
Project: Flink
Issue Type
Kurt Young created FLINK-4490:
-
Summary: Decouple Slot and Instance
Key: FLINK-4490
URL: https://issues.apache.org/jira/browse/FLINK-4490
Project: Flink
Issue Type: Sub-task
Reporter
Kurt Young created FLINK-4442:
-
Summary: Implement Standalone ResourceManager
Key: FLINK-4442
URL: https://issues.apache.org/jira/browse/FLINK-4442
Project: Flink
Issue Type: Sub-task
Kurt Young created FLINK-4430:
-
Summary: prevent BLOCKING partition data lose when task is finished
Key: FLINK-4430
URL: https://issues.apache.org/jira/browse/FLINK-4430
Project: Flink
Issue
Kurt Young created FLINK-4427:
-
Summary: Add slot / container releasing logic to SlotManager
(Standalone / Yarn / Mesos)
Key: FLINK-4427
URL: https://issues.apache.org/jira/browse/FLINK-4427
Project
Kurt Young created FLINK-4373:
-
Summary: Introduce SlotID & ResourceProfile
Key: FLINK-4373
URL: https://issues.apache.org/jira/browse/FLINK-4373
Project: Flink
Issue Type: Sub-
Kurt Young created FLINK-4348:
-
Summary: implement communication from ResourceManager to
TaskManager
Key: FLINK-4348
URL: https://issues.apache.org/jira/browse/FLINK-4348
Project: Flink
Issue
Kurt Young created FLINK-4347:
-
Summary: Implement SlotManager for new ResourceManager
Key: FLINK-4347
URL: https://issues.apache.org/jira/browse/FLINK-4347
Project: Flink
Issue Type: Sub-task
Thanks for the great proposal.
There are still 2 issues i concerned with which i want to discuss with.
#1 Who should decide the resources one operator uses, user or framework?
Like how much cpu or memory will cost by my "map" operator, does it seem a
little bit too low level for the users, should
401 - 460 of 460 matches
Mail list logo
