[jira] [Created] (FLINK-5440) Misleading error message when migrating and scaling down from savepoint

2017-01-10 Thread Ufuk Celebi (JIRA)
Ufuk Celebi created FLINK-5440: -- Summary: Misleading error message when migrating and scaling down from savepoint Key: FLINK-5440 URL: https://issues.apache.org/jira/browse/FLINK-5440 Project: Flink

[jira] [Created] (FLINK-5441) Directly allow SQL queries on a Table

2017-01-10 Thread Timo Walther (JIRA)
Timo Walther created FLINK-5441: --- Summary: Directly allow SQL queries on a Table Key: FLINK-5441 URL: https://issues.apache.org/jira/browse/FLINK-5441 Project: Flink Issue Type: New Feature

Re: Slow duplicated tests

2017-01-10 Thread Aljoscha Krettek
Thanks for looking into this! I think we can put in the fix and remove one of the tests, yes. @Robert What do you think? I think you initially added this test a lng while back. On Mon, 9 Jan 2017 at 20:11 Alexey Demin wrote: > Hi, > > I am trying make small review for

[jira] [Created] (FLINK-5435) Cleanup the rules introduced by FLINK-5144 when calcite releases 1.12

2017-01-10 Thread Kurt Young (JIRA)
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

[jira] [Created] (FLINK-5438) Typo in JobGraph generator Exception

2017-01-10 Thread Ufuk Celebi (JIRA)
Ufuk Celebi created FLINK-5438: -- Summary: Typo in JobGraph generator Exception Key: FLINK-5438 URL: https://issues.apache.org/jira/browse/FLINK-5438 Project: Flink Issue Type: Improvement

Re: [DISCUSS] Improvements to flink's cost based optimizer

2017-01-10 Thread Fabian Hueske
Hi Kurt, thanks for starting this discussion! Although, we use Calcite's cost based optimizer we do not use its full potential. As you correctly identified, this is mainly due to the lack of reliable statistics. Moreover, we use Calcite only for logical optimization, i.e., the optimizer basically

Re: [DISCUSS] proposal for the User Defined AGGregate (UDAGG)

2017-01-10 Thread Fabian Hueske
Hi Shaoxuan, user-defined aggregates would be a great addition to the Table API / SQL. I completely agree that the current (internal) interface is not well suited as an external interface and needs to be redesigned if exposed to users. We need to careful think about this new interface and how we

Re: Slow duplicated tests

2017-01-10 Thread Robert Metzger
I think the code has been refactored many times since then. If the code of the tests is really the same I'm okay with deleting the duplicate method. On Tue, Jan 10, 2017 at 3:29 PM, Aljoscha Krettek wrote: > Thanks for looking into this! I think we can put in the fix and

[DISCUSS] proposal for the User Defined AGGregate (UDAGG)

2017-01-10 Thread Shaoxuan Wang
Hello everyone, I am writing this email to propose a new User Defined Aggregate interface. We were trying to leverage the existing Aggregate interface, but unfortunately we realized that it is not sufficient to meet all our needs. Here are the obstacles we have observed: 1) The current aggregate

[jira] [Created] (FLINK-5437) Make CheckpointedRestoring error message more detailed

2017-01-10 Thread Ufuk Celebi (JIRA)
Ufuk Celebi created FLINK-5437: -- Summary: Make CheckpointedRestoring error message more detailed Key: FLINK-5437 URL: https://issues.apache.org/jira/browse/FLINK-5437 Project: Flink Issue Type:

[jira] [Created] (FLINK-5436) UDF state without CheckpointedRestoring can result in restarting loop

2017-01-10 Thread Ufuk Celebi (JIRA)
Ufuk Celebi created FLINK-5436: -- Summary: UDF state without CheckpointedRestoring can result in restarting loop Key: FLINK-5436 URL: https://issues.apache.org/jira/browse/FLINK-5436 Project: Flink

[jira] [Created] (FLINK-5439) Adjust max parallelism when migrating

2017-01-10 Thread Ufuk Celebi (JIRA)
Ufuk Celebi created FLINK-5439: -- Summary: Adjust max parallelism when migrating Key: FLINK-5439 URL: https://issues.apache.org/jira/browse/FLINK-5439 Project: Flink Issue Type: Improvement

Re: Slow duplicated tests

2017-01-10 Thread Alexey Demin
Hi https://github.com/apache/flink/pull/3089 Check please 2017-01-10 18:42 GMT+04:00 Robert Metzger : > I think the code has been refactored many times since then. > > If the code of the tests is really the same I'm okay with deleting the > duplicate method. > > On Tue,

Re: [DISCUSS] Proposed updates to Flink project site

2017-01-10 Thread Kostas Tzoumas
Love it! I would merge this asap Some comments (not blockers) - I was looking for the downloads page for a minute, until I saw that it is linked via the big blue button :) Did anyone have the same problem? - Do we still link to the wiki? - Maybe too much info is buried under the Community &

Re: time format for akka status

2017-01-10 Thread Till Rohrmann
Hi Alexey, I agree with your proposal to use "-MM-dd HH:mm:ss" or even "-MM-ddTHH:mm:ss" to follow the ISO standard per default but still give the user the possibility to configure it. Cheers, Till On Mon, Jan 9, 2017 at 7:10 PM, Alexey Demin wrote: > Hi, Till > >

Re: [DISCUSS] Proposed updates to Flink project site

2017-01-10 Thread Till Rohrmann
Great work Mike :-) I like the new web page a lot. Some comments: - Can we put a higher resolved Flink logo picture. Looks not good on my monitor and mobile - When browsing the web page on my phone, I noticed that all nav bar items start at the very left border. Maybe some kind of padding would

Re: [DISCUSS] Proposed updates to Flink project site

2017-01-10 Thread Mike Winters
Thanks for the comments, Ufuk. -I rearranged the front page so that the blog posts come before 'Powered By' logos--I think this makes sense. -Nav bar highlights issue is fixed Just pushed these changes, and the preview site ( https://wints.github.io/flink-web/) has been updated as well. Best,

[jira] [Created] (FLINK-5434) Remove unsupported project() transformation from Scala DataStream docs

2017-01-10 Thread Vasia Kalavri (JIRA)
Vasia Kalavri created FLINK-5434: Summary: Remove unsupported project() transformation from Scala DataStream docs Key: FLINK-5434 URL: https://issues.apache.org/jira/browse/FLINK-5434 Project: Flink

答复: [DISCUSS] Apache Flink 1.2.0 RC0 (Non-voting testing release candidate)

2017-01-10 Thread shijinkui
Do we have a probable time of 1.2 release? This month or Next month? -邮件原件- 发件人: Robert Metzger [mailto:rmetz...@apache.org] 发送时间: 2017年1月3日 20:44 收件人: dev@flink.apache.org 抄送: u...@flink.apache.org 主题: [DISCUSS] Apache Flink 1.2.0 RC0 (Non-voting testing release candidate) Hi, First

[jira] [Created] (FLINK-5433) initiate function of Aggregate does not take effect for DataStream aggregation

2017-01-10 Thread Shaoxuan Wang (JIRA)
Shaoxuan Wang created FLINK-5433: Summary: initiate function of Aggregate does not take effect for DataStream aggregation Key: FLINK-5433 URL: https://issues.apache.org/jira/browse/FLINK-5433

Re: [DISCUSS] Proposed updates to Flink project site

2017-01-10 Thread Ufuk Celebi
Thanks for addressing my comments. I really like the new web site! If there are no objections, I would like to merge this later today. On Tue, Jan 10, 2017 at 11:56 AM, Mike Winters wrote: > Thanks for the comments, Ufuk. > > -I rearranged the front page so that the blog

Re: 答复: [DISCUSS] Apache Flink 1.2.0 RC0 (Non-voting testing release candidate)

2017-01-10 Thread Robert Metzger
Hi, this depends a lot on the number of issues we find during the testing. These are the issues I found so far: https://issues.apache.org/jira/browse/FLINK-5379 (unresolved) https://issues.apache.org/jira/browse/FLINK-5383 (resolved) https://issues.apache.org/jira/browse/FLINK-5382 (resolved)

Re: [DISCUSS] ElasticSearch in Flink Strategy

2017-01-10 Thread Robert Metzger
I definitively agree, if we can cover the functionality with all ES dependency versions. On Tue, Jan 10, 2017 at 6:50 AM, Tzu-Li (Gordon) Tai wrote: > Hi, > > As part of restructuring the ES connectors, I think it also a very good > timing to unify how our ES connectors are

[DISCUSS] Improvements to flink's cost based optimizer

2017-01-10 Thread Kurt Young
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: