date:20190711

Kurt Young created FLINK-13208:
--

 Summary: Add Notice file for upgrading calcite to 1.20
 Key: FLINK-13208
 URL: https://issues.apache.org/jira/browse/FLINK-13208
 Project: Flink
  Issue Type: Task
  Components: Table SQL / Legacy Planner, Table SQL / Planner
Reporter: Kurt Young
Assignee: Kurt Young






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13209) Following FLINK-12951: Remove TableEnvironment#sql and add create table ddl support to sqlUpdate

2019-07-11 Thread Danny Chan (JIRA)

Danny Chan created FLINK-13209:
--

 Summary: Following FLINK-12951: Remove TableEnvironment#sql and 
add create table ddl support to sqlUpdate
 Key: FLINK-13209
 URL: https://issues.apache.org/jira/browse/FLINK-13209
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / API
Affects Versions: 1.9.0
Reporter: Danny Chan
Assignee: Danny Chan
 Fix For: 1.9.0






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[DISCUSS] Create "flink-playgrounds" repository

2019-07-11 Thread Konstantin Knauf

Hi everyone,

in the course of implementing FLIP-42 we are currently reworking the
Getting Started section of our documentation. As part of this, we are
adding docker-compose-based playgrounds to get started with Flink
operations and Flink SQL quickly.

To reduce as much friction as possible for new users, we would like to
maintain the required configuration files (docker-comose.yaml,
flink-conf.yaml) in a separate new repository, `apache/flink-playgrounds`.

You can find more details and a brief discussion on this in the
corresponding Jira ticket [2].

What do you think?

I am not sure, what kind of approval is required for such a change. So, my
suggestion would be that we have lazy majority within the next 24 hours to
create the repository, we proceed. Please let me know, if this requires a
more formal approval.

Best and thanks,

Konstantin

[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-42%3A+Rework+Flink+Documentation
[2] https://issues.apache.org/jira/browse/FLINK-12749


-- 

Konstantin Knauf | Solutions Architect

+49 160 91394525


Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010


--

Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany

--

Ververica GmbH
Registered at Amtsgericht Charlottenburg: HRB 158244 B
Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen

[jira] [Created] (FLINK-13210) Hive connector test should dependent on blink planner instead of legacy planner

Jingsong Lee created FLINK-13210:


 Summary: Hive connector test should dependent on blink planner 
instead of legacy planner
 Key: FLINK-13210
 URL: https://issues.apache.org/jira/browse/FLINK-13210
 Project: Flink
  Issue Type: Improvement
  Components: Connectors / Hive
Reporter: Jingsong Lee
Assignee: Bowen Li


Blink planner has more support and more functions, and some ITCase will not be 
able to measure it without relying on Blink-planner in test.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13211) Add drop table support for flink planner

2019-07-11 Thread Danny Chan (JIRA)

Danny Chan created FLINK-13211:
--

 Summary: Add drop table support for flink planner
 Key: FLINK-13211
 URL: https://issues.apache.org/jira/browse/FLINK-13211
 Project: Flink
  Issue Type: Improvement
  Components: Table SQL / Planner
Affects Versions: 1.9.0
Reporter: Danny Chan
Assignee: Danny Chan
 Fix For: 1.9.0






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Request for access

2019-07-11 Thread 袁智翔

Hi,

I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA username is zhixiangyuan.

Re: [DISCUSS] Create "flink-playgrounds" repository

2019-07-11 Thread Robert Metzger

+1 to create a repo.

On Thu, Jul 11, 2019 at 11:10 AM Konstantin Knauf 
wrote:

> Hi everyone,
>
> in the course of implementing FLIP-42 we are currently reworking the
> Getting Started section of our documentation. As part of this, we are
> adding docker-compose-based playgrounds to get started with Flink
> operations and Flink SQL quickly.
>
> To reduce as much friction as possible for new users, we would like to
> maintain the required configuration files (docker-comose.yaml,
> flink-conf.yaml) in a separate new repository, `apache/flink-playgrounds`.
>
> You can find more details and a brief discussion on this in the
> corresponding Jira ticket [2].
>
> What do you think?
>
> I am not sure, what kind of approval is required for such a change. So, my
> suggestion would be that we have lazy majority within the next 24 hours to
> create the repository, we proceed. Please let me know, if this requires a
> more formal approval.
>
> Best and thanks,
>
> Konstantin
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-42%3A+Rework+Flink+Documentation
> [2] https://issues.apache.org/jira/browse/FLINK-12749
>
>
> --
>
> Konstantin Knauf | Solutions Architect
>
> +49 160 91394525
>
>
> Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
>
>
> --
>
> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
>
> --
>
> Ververica GmbH
> Registered at Amtsgericht Charlottenburg: HRB 158244 B
> Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
>

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.9.0 release

2019-07-11 Thread Chesnay Schepler

Can we get JIRA's attached to these items so people out of the loop can
track the progress?

On 05/07/2019 16:06, Kurt Young wrote:

Here are the features I collected which are under actively developing and
close
to merge:

1. Bridge blink planner to unified table environment and remove TableConfig
from blink planner
2. Support timestamp with local time zone and partition pruning in blink
planner
3. Support JDBC & HBase lookup function and upsert sink
4. StreamExecutionEnvironment supports executing job with StreamGraph, and
blink planner should set proper properties to StreamGraph
5. Set resource profiles to task and enable managed memory as resource
profile

Best,
Kurt

On Fri, Jul 5, 2019 at 9:37 PM Kurt Young wrote:

Hi devs,

It's July 5 now and we should announce feature freeze and cut the branch
as planned. However, some components seems still not ready yet and
various features are still under development or review.

But we also can not extend the freeze day again which will further delay
the
release date. I think freeze new features today and have another couple
of buffer days, letting features which are almost ready have a chance to
get in is a reasonable solution.

I hereby announce features of Flink 1.9.0 are freezed, *July 11* will be
the
day for cutting branch. Since the feature freeze has effectively took
place,
I kindly ask committers to refrain from merging features that are planned
for
future releases into the master branch for the time being before the 1.9
branch
is cut. We understand this might be a bit inconvenient, thanks for the
cooperation here.

Best,
Kurt

On Fri, Jul 5, 2019 at 5:19 PM 罗齐 wrote:

Hi Gordon,

Will branch 1.9 be cut out today? We're really looking forward to the
blink features in 1.9.

Thanks,
Qi

On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai
wrote:

Thanks for the updates so far everyone!

Since support for the new Blink-based Table / SQL runner and fine-grained
recovery are quite prominent features for 1.9.0,
and developers involved in these topics have already expressed that these
could make good use for another week,
I think it definitely makes sense to postpone the feature freeze.

The new date for feature freeze and feature branch cut for 1.9.0 will be
*July
5*.

Please update on this thread if there are any further concerns!

Cheers,
Gordon

On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler
wrote:

On the fine-grained recovery / batch scheduling side we could make good
use of another week.
Currently we are on track to have the _feature_ merged, but without
having done a great deal of end-to-end testing.

On 25/06/2019 15:01, Kurt Young wrote:

Hi Aljoscha,

I also feel an additional week can make the remaining work more

easy. At

least
we don't have to check in lots of commits in both branches (master &
release-1.9).

Best,
Kurt

On Tue, Jun 25, 2019 at 8:27 PM Aljoscha Krettek <

aljos...@apache.org>

wrote:

A few threads are converging around supporting the new Blink-based

Table

API Runner/Planner. I think hitting the currently proposed feature

freeze

date is hard, if not impossible, and that the work would benefit

from an

additional week to get everything in with good quality.

What do the others involved in the topic think?

Aljoscha

On 24. Jun 2019, at 19:42, Bowen Li wrote:

Hi Gordon,

Thanks for driving this effort.

Xuefu responded to the discussion thread [1] and I want to bring

that

our attention here:

Hive integration depends on a few features that are actively

developed.

the completion of those features don't leave enough time for us to
integrate, then our work can potentially go beyond the proposed

date.

Just wanted to point out such a dependency adds uncertainty.

[1]

http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Features-for-Apache-Flink-1-9-0-td28701.html

On Thu, Jun 20, 2019 at 1:05 AM Tzu-Li (Gordon) Tai <

tzuli...@apache.org

wrote:

Hi devs,

Per the feature discussions for 1.9.0 [1], I hereby announce the

official

feature freeze for Flink 1.9.0 to be on June 28. A release feature

branch

for 1.9 will be cut following that date.

We’re roughly one week away from this date, but please keep in

mind

that we

still shouldn’t rush things. If you feel that there may be

problems

with

this schedule for the things you are working on, please let us

know

here.

Cheers,
Gordon

[1]

http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Features-for-Apache-Flink-1-9-0-td28701.html

Re: [DISCUSS] Create "flink-playgrounds" repository

2019-07-11 Thread Fabian Hueske

Hi,

I think Quickstart should be as lightweight as possible and follow common
practices.
A Git repository for a few configuration files might feel like overkill,
but IMO it makes sense because this ensures users can get started with 3
commands:

$ git clone .../flink-playground
$ cd flink-playground
$ docker-compose up -d

So +1 to create a repository.

Thanks, Fabian

Am Do., 11. Juli 2019 um 12:07 Uhr schrieb Robert Metzger <
rmetz...@apache.org>:

> +1 to create a repo.
>
> On Thu, Jul 11, 2019 at 11:10 AM Konstantin Knauf <
> konstan...@ververica.com>
> wrote:
>
> > Hi everyone,
> >
> > in the course of implementing FLIP-42 we are currently reworking the
> > Getting Started section of our documentation. As part of this, we are
> > adding docker-compose-based playgrounds to get started with Flink
> > operations and Flink SQL quickly.
> >
> > To reduce as much friction as possible for new users, we would like to
> > maintain the required configuration files (docker-comose.yaml,
> > flink-conf.yaml) in a separate new repository,
> `apache/flink-playgrounds`.
> >
> > You can find more details and a brief discussion on this in the
> > corresponding Jira ticket [2].
> >
> > What do you think?
> >
> > I am not sure, what kind of approval is required for such a change. So,
> my
> > suggestion would be that we have lazy majority within the next 24 hours
> to
> > create the repository, we proceed. Please let me know, if this requires a
> > more formal approval.
> >
> > Best and thanks,
> >
> > Konstantin
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-42%3A+Rework+Flink+Documentation
> > [2] https://issues.apache.org/jira/browse/FLINK-12749
> >
> >
> > --
> >
> > Konstantin Knauf | Solutions Architect
> >
> > +49 160 91394525
> >
> >
> > Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
> >
> >
> > --
> >
> > Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> >
> > --
> >
> > Ververica GmbH
> > Registered at Amtsgericht Charlottenburg: HRB 158244 B
> > Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
> >
>

[jira] [Created] (FLINK-13212) Unstable ChainLengthIncreaseTest

Kurt Young created FLINK-13212:
--

 Summary: Unstable ChainLengthIncreaseTest
 Key: FLINK-13212
 URL: https://issues.apache.org/jira/browse/FLINK-13212
 Project: Flink
  Issue Type: Test
  Components: Tests
Reporter: Kurt Young


10:05:29.300 [ERROR] 
ChainLengthIncreaseTest>AbstractOperatorRestoreTestBase.testMigrationAndRestore:102->AbstractOperatorRestoreTestBase.migrateJob:138
 » Execution
10:05:29.301 [ERROR] 
ChainLengthIncreaseTest>AbstractOperatorRestoreTestBase.testMigrationAndRestore:102->AbstractOperatorRestoreTestBase.migrateJob:138
 » Execution
 
More details in: [https://api.travis-ci.org/v3/job/557222905/log.txt]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13213) MinIdleStateRetentionTime/MaxIdleStateRetentionTime in TableConfig will be removed after call toAppendStream/toRetractStream without QueryConfig parameters

2019-07-11 Thread Jing Zhang (JIRA)

Jing Zhang created FLINK-13213:
--

 Summary: MinIdleStateRetentionTime/MaxIdleStateRetentionTime in 
TableConfig will be removed after call toAppendStream/toRetractStream without 
QueryConfig parameters
 Key: FLINK-13213
 URL: https://issues.apache.org/jira/browse/FLINK-13213
 Project: Flink
  Issue Type: Task
  Components: Table SQL / API
Reporter: Jing Zhang
Assignee: Jing Zhang


There are two `toAppendStream` method in `StreamTableEnvironment`:
1.  def toAppendStream[T: TypeInformation](table: Table): DataStream[T]
2.   def toAppendStream[T: TypeInformation](table: Table, queryConfig: 
StreamQueryConfig): DataStream[T]

After convert `Table` to `DataStream` by call the first method or 
toRetractStream, the MinIdleStateRetentionTime/MaxIdleStateRetentionTime in 
TableConfig will be removed.




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13214) Hive connectors does not compile with Java 9

Chesnay Schepler created FLINK-13214:


 Summary: Hive connectors does not compile with Java 9
 Key: FLINK-13214
 URL: https://issues.apache.org/jira/browse/FLINK-13214
 Project: Flink
  Issue Type: Improvement
  Components: Connectors / Hive
Affects Versions: 1.9.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.9.0


{code}
[ERROR] Failed to execute goal on project flink-connector-hive_2.12: Could not 
resolve dependencies for project 
org.apache.flink:flink-connector-hive_2.12:jar:1.9-SNAPSHOT: Could not find 
artifact jdk.tools:jdk.tools:jar:1.7 at specified path 
C:\Dev\Java\9/../lib/tools.jar -> [Help 1]
{code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13215) Hive connector does not compile on Java 9

Chesnay Schepler created FLINK-13215:


 Summary: Hive connector does not compile on Java 9
 Key: FLINK-13215
 URL: https://issues.apache.org/jira/browse/FLINK-13215
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Hive
Affects Versions: 1.9.0
Reporter: Chesnay Schepler
 Fix For: 1.9.0


{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile 
(default-testCompile) on project flink-connector-hive_2.11: Compilation failure
[ERROR] 
/C:/Dev/Repos/flink/flink-connectors/flink-connector-hive/src/test/java/org/apache/flink/batch/connectors/hive/FlinkStandaloneHiveRunner.java:[56,15]
 package sun.net.www is not visible
{code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13216) AggregateITCase.testNestedGroupByAgg fails on Travis

2019-07-11 Thread Till Rohrmann (JIRA)

Till Rohrmann created FLINK-13216:
-

 Summary: AggregateITCase.testNestedGroupByAgg fails on Travis
 Key: FLINK-13216
 URL: https://issues.apache.org/jira/browse/FLINK-13216
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Planner
Affects Versions: 1.9.0
Reporter: Till Rohrmann
 Fix For: 1.9.0


The {{AggregateITCase.testNestedGroupByAgg}} fails on Travis with

{code}
AggregateITCase.testNestedGroupByAgg:472 expected: but was:
{code}

https://api.travis-ci.org/v3/job/557214216/log.txt



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13217) Blink planner does not compile with Scala 2.12

Chesnay Schepler created FLINK-13217:


 Summary: Blink planner does not compile with Scala 2.12
 Key: FLINK-13217
 URL: https://issues.apache.org/jira/browse/FLINK-13217
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Planner
Affects Versions: 1.9.0
Reporter: Chesnay Schepler
 Fix For: 1.9.0


{code}
[ERROR] 
C:\Dev\Repos\flink\flink-table\flink-table-planner-blink\src\main\scala\org\apache\flink\table\calcite\FlinkLogicalRelFactories.scala:111:
 error: overriding method createSort in trait SortFactory of type (x$1: 
org.apache.calcite.plan.RelTraitSet, x$2: org.apache.calcite.rel.RelNode, x$3: 
org.apache.calcite.rel.RelCollation, x$4: org.apache.calcite.rex.RexNode, x$5: 
org.apache.calcite.rex.RexNode)org.apache.calcite.rel.RelNode;
[ERROR]  method createSort needs `override' modifier
[ERROR] def createSort(
[ERROR] ^
[ERROR] 
C:\Dev\Repos\flink\flink-table\flink-table-planner-blink\src\main\scala\org\apache\flink\table\calcite\FlinkLogicalRelFactories.scala:181:
 error: overriding method createJoin in trait JoinFactory of type (x$1: 
org.apache.calcite.rel.RelNode, x$2: org.apache.calcite.rel.RelNode, x$3: 
org.apache.calcite.rex.RexNode, x$4: org.apache.calcite.rel.core.JoinRelType, 
x$5: java.util.Set[String], x$6: Boolean)org.apache.calcite.rel.RelNode;
[ERROR]  method createJoin needs `override' modifier
[ERROR] def createJoin(
[ERROR] ^
{code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13218) '*.count not supported in TableApi query

2019-07-11 Thread Jing Zhang (JIRA)

Jing Zhang created FLINK-13218:
--

 Summary: '*.count not supported in TableApi query
 Key: FLINK-13218
 URL: https://issues.apache.org/jira/browse/FLINK-13218
 Project: Flink
  Issue Type: Task
Reporter: Jing Zhang
Assignee: Jing Zhang


The following query is not supported yet:

{code:java}
val t = StreamTestData.get3TupleDataStream(env).toTable(tEnv, 'a, 'b, 'c)
  .groupBy('b)
  .select('b, 'a.sum, '*.count)
{code}

The following exception will be thrown.

{code:java}
org.apache.flink.table.api.ValidationException: Cannot resolve field [*], input 
field list:[a, b, c].

at 
org.apache.flink.table.expressions.resolver.rules.ReferenceResolverRule$ExpressionResolverVisitor.failForField(ReferenceResolverRule.java:80)
at 
org.apache.flink.table.expressions.resolver.rules.ReferenceResolverRule$ExpressionResolverVisitor.lambda$null$4(ReferenceResolverRule.java:75)
at java.util.Optional.orElseThrow(Optional.java:290)
at 
org.apache.flink.table.expressions.resolver.rules.ReferenceResolverRule$ExpressionResolverVisitor.lambda$null$5(ReferenceResolverRule.java:75)
at java.util.Optional.orElseGet(Optional.java:267)
at 
org.apache.flink.table.expressions.resolver.rules.ReferenceResolverRule$ExpressionResolverVisitor.lambda$visit$6(ReferenceResolverRule.java:74)
at java.util.Optional.orElseGet(Optional.java:267)
at 
org.apache.flink.table.expressions.resolver.rules.ReferenceResolverRule$ExpressionResolverVisitor.visit(ReferenceResolverRule.java:71)
at 
org.apache.flink.table.expressions.resolver.rules.ReferenceResolverRule$ExpressionResolverVisitor.visit(ReferenceResolverRule.java:51)
at 
...
{code}




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13219) Hive connector fails hadoop 2.4.1 builds

Chesnay Schepler created FLINK-13219:


 Summary: Hive connector fails hadoop 2.4.1 builds
 Key: FLINK-13219
 URL: https://issues.apache.org/jira/browse/FLINK-13219
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Hive
Affects Versions: 1.9.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.9.0


The hive connector does not work with hadoop 2.4, but the tests are still run 
in the corresponding cron profile.

https://travis-ci.org/apache/flink/jobs/555723021

We should add a profile for skipping the hive tests that we enable for these 
profiles.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13220) Add DDL support for blink planner

2019-07-11 Thread Danny Chan (JIRA)

Danny Chan created FLINK-13220:
--

 Summary: Add DDL support for blink planner
 Key: FLINK-13220
 URL: https://issues.apache.org/jira/browse/FLINK-13220
 Project: Flink
  Issue Type: Improvement
  Components: Table SQL / Planner
Affects Versions: 1.9.0
Reporter: Danny Chan
Assignee: Danny Chan
 Fix For: 1.9.0






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13221) Blink planner should set ScheduleMode to LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST for batch jobs

Kurt Young created FLINK-13221:
--

 Summary: Blink planner should set ScheduleMode to 
LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST for batch jobs
 Key: FLINK-13221
 URL: https://issues.apache.org/jira/browse/FLINK-13221
 Project: Flink
  Issue Type: Improvement
  Components: Table SQL / Planner
Reporter: Kurt Young






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13222) Add documentation for AdaptedRestartPipelinedRegionStrategyNG

2019-07-11 Thread Gary Yao (JIRA)

Gary Yao created FLINK-13222:


 Summary: Add documentation for 
AdaptedRestartPipelinedRegionStrategyNG
 Key: FLINK-13222
 URL: https://issues.apache.org/jira/browse/FLINK-13222
 Project: Flink
  Issue Type: Task
  Components: Runtime / Coordination
Reporter: Gary Yao


It should be documented that if {{jobmanager.execution.failover-strategy}} is 
set to _region_, the new pipelined region failover strategy 
({{AdaptedRestartPipelinedRegionStrategyNG}}) will be used. 

*Acceptance Criteria*
* config values _region_ and _full_ are documented
* to be decided: config values _region-legacy_ and _individual_ remain 
undocumented



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13223) Set jobmanager.execution.failover-strategy to region in default flink-conf.yaml

2019-07-11 Thread Gary Yao (JIRA)

Gary Yao created FLINK-13223:


 Summary: Set jobmanager.execution.failover-strategy to region in 
default flink-conf.yaml
 Key: FLINK-13223
 URL: https://issues.apache.org/jira/browse/FLINK-13223
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Coordination
Reporter: Gary Yao
Assignee: Gary Yao


Set jobmanager.execution.failover-strategy to region in default flink-conf.yaml



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [DISCUSS] Flink project bylaws

2019-07-11 Thread Robert Metzger

Thank you Becket for kicking off this discussion and creating a draft in
the Wiki.

I left some comments in the wiki.

In my understanding this means, that a committer always needs a review and
> +1 from another committer. As far as I know this is currently not always
> the case (often committer authors, contributor reviews & +1s).


I would agree to add such a bylaw, if we had cases in the past where code
was not sufficiently reviewed AND we believe that we have enough capacity
to ensure a separate committer's approval.





On Thu, Jul 11, 2019 at 9:49 AM Konstantin Knauf 
wrote:

> Hi all,
>
> thanks a lot for driving this, Becket. I have two remarks regarding the
> "Actions" section:
>
> * In addition to a simple "Code Change" we could also add a row for "Code
> Change requiring a FLIP" with a reference to the FLIP process page. A FLIP
> will have/does have different rules for approvals, etc.
> * For "Code Change" the draft currently requires "one +1 from a committer
> who has not authored the patch followed by a Lazy approval (not counting
> the vote of the contributor), moving to lazy majority if a -1 is received".
> In my understanding this means, that a committer always needs a review and
> +1 from another committer. As far as I know this is currently not always
> the case (often committer authors, contributor reviews & +1s).
>
> I think it is worth thinking about how we can make it easy to follow the
> bylaws e.g. by having more Flink-specific Jira workflows and ticket types +
> corresponding permissions. While this is certainly "Step 2", I believe, we
> really need to make it as easy & transparent as possible, otherwise they
> will be unintentionally broken.
>
> Cheers and thanks,
>
> Konstantin
>
>
>
> On Thu, Jul 11, 2019 at 9:10 AM Becket Qin  wrote:
>
> > Hi all,
> >
> > As it was raised in the FLIP process discussion thread [1], currently
> Flink
> > does not have official bylaws to govern the operation of the project.
> Such
> > bylaws are critical for the community to coordinate and contribute
> > together. It is also the basis of other processes such as FLIP.
> >
> > I have drafted a Flink bylaws page and would like to start a discussion
> > thread on this.
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120731026
> >
> > The bylaws will affect everyone in the community. It'll be great to hear
> > your thoughts.
> >
> > Thanks,
> >
> > Jiangjie (Becket) Qin
> >
> > [1]
> >
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-META-FLIP-Sticking-or-not-to-a-strict-FLIP-voting-process-td29978.html#none
> >
>
>
> --
>
> Konstantin Knauf | Solutions Architect
>
> +49 160 91394525
>
>
> Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
>
>
> --
>
> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
>
> --
>
> Ververica GmbH
> Registered at Amtsgericht Charlottenburg: HRB 158244 B
> Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
>

[jira] [Created] (FLINK-13224) TupleTypeInfoBase equals function can't distinguish different struct type

2019-07-11 Thread forideal (JIRA)

forideal created FLINK-13224:


 Summary: TupleTypeInfoBase equals function can't distinguish 
different struct type
 Key: FLINK-13224
 URL: https://issues.apache.org/jira/browse/FLINK-13224
 Project: Flink
  Issue Type: Bug
Affects Versions: 1.8.0
 Environment: flink 1.8.0
Reporter: forideal


Hi

i have two struct type

one is
{code:java}
// code placeholder
Types.ROW_NAMED(
         new String[]{"device"},
         Types.PRIMITIVE_ARRAY(Types.BYTE)

)
{code}
the other is

 
{code:java}
// code placeholder
Types.ROW_NAMED(
         new String[]{"app"},
         Types.PRIMITIVE_ARRAY(Types.BYTE)

)
{code}
when i compare those two types ,the equals function returns true.

there are some code in TupleTypeInfoBase         
{code:java}
// code placeholder
return other.canEqual(this) &&
           super.equals(other) &&
   Arrays.equals(types, other.types) &&
   totalFields == other.totalFields;
{code}
i think,The equals function should compare field names.

eg:
{code:java}
// code placeholder
if (totalFields == other.totalFields) {
 String[] otherFieldNames = other.getFieldNames();
 String[] fieldNames = this.getFieldNames();
 for (int i = 0; i < totalFields; i++) {
 if (!otherFieldNames[i].equals(fieldNames[i])) {
 return false;
 }
 }
 } else{
   return false;
 }

return other.canEqual(this) &&
   super.equals(other) &&
   Arrays.equals(types, other.types);
{code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [DISCUSS] Flink project bylaws

2019-07-11 Thread Chesnay Schepler

The emeritus stuff seems like unnecessary noise.

There's a bunch of subtle changes in the draft compared to existing
"conventions"; we should find a way to highlight these and discuss them
one by one.

On 11/07/2019 14:29, Robert Metzger wrote:

Thank you Becket for kicking off this discussion and creating a draft in
the Wiki.

I left some comments in the wiki.

In my understanding this means, that a committer always needs a review and

+1 from another committer. As far as I know this is currently not always
the case (often committer authors, contributor reviews & +1s).

I would agree to add such a bylaw, if we had cases in the past where code
was not sufficiently reviewed AND we believe that we have enough capacity
to ensure a separate committer's approval.

On Thu, Jul 11, 2019 at 9:49 AM Konstantin Knauf
wrote:

Hi all,

thanks a lot for driving this, Becket. I have two remarks regarding the
"Actions" section:

* In addition to a simple "Code Change" we could also add a row for "Code
Change requiring a FLIP" with a reference to the FLIP process page. A FLIP
will have/does have different rules for approvals, etc.
* For "Code Change" the draft currently requires "one +1 from a committer
who has not authored the patch followed by a Lazy approval (not counting
the vote of the contributor), moving to lazy majority if a -1 is received".
In my understanding this means, that a committer always needs a review and
+1 from another committer. As far as I know this is currently not always
the case (often committer authors, contributor reviews & +1s).

I think it is worth thinking about how we can make it easy to follow the
bylaws e.g. by having more Flink-specific Jira workflows and ticket types +
corresponding permissions. While this is certainly "Step 2", I believe, we
really need to make it as easy & transparent as possible, otherwise they
will be unintentionally broken.

Cheers and thanks,

Konstantin

On Thu, Jul 11, 2019 at 9:10 AM Becket Qin wrote:

Hi all,

As it was raised in the FLIP process discussion thread [1], currently

Flink

does not have official bylaws to govern the operation of the project.

Such

bylaws are critical for the community to coordinate and contribute
together. It is also the basis of other processes such as FLIP.

I have drafted a Flink bylaws page and would like to start a discussion
thread on this.

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120731026

The bylaws will affect everyone in the community. It'll be great to hear
your thoughts.

Thanks,

Jiangjie (Becket) Qin

[1]

http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-META-FLIP-Sticking-or-not-to-a-strict-FLIP-voting-process-td29978.html#none

Konstantin Knauf | Solutions Architect

+49 160 91394525

Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010

Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany

Ververica GmbH
Registered at Amtsgericht Charlottenburg: HRB 158244 B
Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen

[jira] [Created] (FLINK-13225) Introduce type inference for hive functions in blink

Jingsong Lee created FLINK-13225:


 Summary: Introduce type inference for hive functions in blink
 Key: FLINK-13225
 URL: https://issues.apache.org/jira/browse/FLINK-13225
 Project: Flink
  Issue Type: Improvement
  Components: Table SQL / Planner
Reporter: Jingsong Lee
Assignee: Jingsong Lee


See some conversation in [https://github.com/apache/flink/pull/8920]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [DISCUSS] Flink project bylaws

2019-07-11 Thread Till Rohrmann

Thanks a lot for creating this draft Becket.

I think without the notion of emeritus (or active vs. inactive), it won't
be possible to have a 2/3 majority vote because we already have too many
inactive PMCs/committers.

For the case of a committer being the author and getting a +1 from a
non-committer: I think a committer should know when to ask another
committer for feedback or not. Hence, I would not enforce that we strictly
need a +1 from a committer if the author is a committer but of course
encourage it if capacities exist.

Cheers,
Till

On Thu, Jul 11, 2019 at 3:08 PM Chesnay Schepler  wrote:

> The emeritus stuff seems like unnecessary noise.
>
> There's a bunch of subtle changes in the draft compared to existing
> "conventions"; we should find a way to highlight these and discuss them
> one by one.
>
> On 11/07/2019 14:29, Robert Metzger wrote:
> > Thank you Becket for kicking off this discussion and creating a draft in
> > the Wiki.
> >
> > I left some comments in the wiki.
> >
> > In my understanding this means, that a committer always needs a review
> and
> >> +1 from another committer. As far as I know this is currently not always
> >> the case (often committer authors, contributor reviews & +1s).
> >
> > I would agree to add such a bylaw, if we had cases in the past where code
> > was not sufficiently reviewed AND we believe that we have enough capacity
> > to ensure a separate committer's approval.
> >
> >
> >
> >
> >
> > On Thu, Jul 11, 2019 at 9:49 AM Konstantin Knauf <
> konstan...@ververica.com>
> > wrote:
> >
> >> Hi all,
> >>
> >> thanks a lot for driving this, Becket. I have two remarks regarding the
> >> "Actions" section:
> >>
> >> * In addition to a simple "Code Change" we could also add a row for
> "Code
> >> Change requiring a FLIP" with a reference to the FLIP process page. A
> FLIP
> >> will have/does have different rules for approvals, etc.
> >> * For "Code Change" the draft currently requires "one +1 from a
> committer
> >> who has not authored the patch followed by a Lazy approval (not counting
> >> the vote of the contributor), moving to lazy majority if a -1 is
> received".
> >> In my understanding this means, that a committer always needs a review
> and
> >> +1 from another committer. As far as I know this is currently not always
> >> the case (often committer authors, contributor reviews & +1s).
> >>
> >> I think it is worth thinking about how we can make it easy to follow the
> >> bylaws e.g. by having more Flink-specific Jira workflows and ticket
> types +
> >> corresponding permissions. While this is certainly "Step 2", I believe,
> we
> >> really need to make it as easy & transparent as possible, otherwise they
> >> will be unintentionally broken.
> >>
> >> Cheers and thanks,
> >>
> >> Konstantin
> >>
> >>
> >>
> >> On Thu, Jul 11, 2019 at 9:10 AM Becket Qin 
> wrote:
> >>
> >>> Hi all,
> >>>
> >>> As it was raised in the FLIP process discussion thread [1], currently
> >> Flink
> >>> does not have official bylaws to govern the operation of the project.
> >> Such
> >>> bylaws are critical for the community to coordinate and contribute
> >>> together. It is also the basis of other processes such as FLIP.
> >>>
> >>> I have drafted a Flink bylaws page and would like to start a discussion
> >>> thread on this.
> >>>
> >>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120731026
> >>> The bylaws will affect everyone in the community. It'll be great to
> hear
> >>> your thoughts.
> >>>
> >>> Thanks,
> >>>
> >>> Jiangjie (Becket) Qin
> >>>
> >>> [1]
> >>>
> >>>
> >>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-META-FLIP-Sticking-or-not-to-a-strict-FLIP-voting-process-td29978.html#none
> >>
> >> --
> >>
> >> Konstantin Knauf | Solutions Architect
> >>
> >> +49 160 91394525
> >>
> >>
> >> Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
> >>
> >>
> >> --
> >>
> >> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> >>
> >> --
> >>
> >> Ververica GmbH
> >> Registered at Amtsgericht Charlottenburg: HRB 158244 B
> >> Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
> >>
>
>

[jira] [Created] (FLINK-13226) KafkaProducerExactlyOnceITCase.testMultipleSinkOperators fails on Travis

2019-07-11 Thread Till Rohrmann (JIRA)

Till Rohrmann created FLINK-13226:
-

 Summary: KafkaProducerExactlyOnceITCase.testMultipleSinkOperators 
fails on Travis
 Key: FLINK-13226
 URL: https://issues.apache.org/jira/browse/FLINK-13226
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Kafka
Affects Versions: 1.9.0
Reporter: Till Rohrmann


The {{KafkaProducerExactlyOnceITCase.testMultipleSinkOperators}} fails on 
Travis with not producing output for 300 s.

https://api.travis-ci.org/v3/job/557290235/log.txt



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13227) Translate "Asynchronous I/O for External Data Access" page into Chinese

2019-07-11 Thread WangHengWei (JIRA)

WangHengWei created FLINK-13227:
---

 Summary: Translate "Asynchronous I/O for External Data Access" 
page into Chinese
 Key: FLINK-13227
 URL: https://issues.apache.org/jira/browse/FLINK-13227
 Project: Flink
  Issue Type: Sub-task
  Components: chinese-translation, Documentation
Affects Versions: 1.8.0, 1.9.0
Reporter: WangHengWei
Assignee: WangHengWei


The page url is 
[https://ci.apache.org/projects/flink/flink-docs-master/dev/stream/operators/asyncio.html]
The markdown file is located in flink/docs/dev/stream/operators/asyncio.md



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13228) HadoopRecoverableWriterTest.testCommitAfterNormalClose fails on Travis

2019-07-11 Thread Till Rohrmann (JIRA)

Till Rohrmann created FLINK-13228:
-

 Summary: HadoopRecoverableWriterTest.testCommitAfterNormalClose 
fails on Travis
 Key: FLINK-13228
 URL: https://issues.apache.org/jira/browse/FLINK-13228
 Project: Flink
  Issue Type: Bug
  Components: FileSystems
Affects Versions: 1.9.0
Reporter: Till Rohrmann


{{HadoopRecoverableWriterTest.testCommitAfterNormalClose}} failed on Travis with

{code}
HadoopRecoverableWriterTest.testCommitAfterNormalClose Â» IO The stream is 
closed
{code}

https://api.travis-ci.org/v3/job/557293706/log.txt



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13229) ExpressionReducer with udf bug in blink

Jingsong Lee created FLINK-13229:


 Summary: ExpressionReducer with udf bug in blink
 Key: FLINK-13229
 URL: https://issues.apache.org/jira/browse/FLINK-13229
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Planner
Reporter: Jingsong Lee
Assignee: Jingsong Lee


When a udf is reduced by ExpressionReducer, there will be a code gen exception.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [DISCUSS] Create "flink-playgrounds" repository

2019-07-11 Thread Stephan Ewen

Hi all!

I am fine with a separate repository.

Quick question. though: Have you considered putting the setup not under
"docs" but under "flink-quickstart" or so?
Would that be equally cumbersome for users?

Best,
Stephan


On Thu, Jul 11, 2019 at 12:19 PM Fabian Hueske  wrote:

> Hi,
>
> I think Quickstart should be as lightweight as possible and follow common
> practices.
> A Git repository for a few configuration files might feel like overkill,
> but IMO it makes sense because this ensures users can get started with 3
> commands:
>
> $ git clone .../flink-playground
> $ cd flink-playground
> $ docker-compose up -d
>
> So +1 to create a repository.
>
> Thanks, Fabian
>
> Am Do., 11. Juli 2019 um 12:07 Uhr schrieb Robert Metzger <
> rmetz...@apache.org>:
>
> > +1 to create a repo.
> >
> > On Thu, Jul 11, 2019 at 11:10 AM Konstantin Knauf <
> > konstan...@ververica.com>
> > wrote:
> >
> > > Hi everyone,
> > >
> > > in the course of implementing FLIP-42 we are currently reworking the
> > > Getting Started section of our documentation. As part of this, we are
> > > adding docker-compose-based playgrounds to get started with Flink
> > > operations and Flink SQL quickly.
> > >
> > > To reduce as much friction as possible for new users, we would like to
> > > maintain the required configuration files (docker-comose.yaml,
> > > flink-conf.yaml) in a separate new repository,
> > `apache/flink-playgrounds`.
> > >
> > > You can find more details and a brief discussion on this in the
> > > corresponding Jira ticket [2].
> > >
> > > What do you think?
> > >
> > > I am not sure, what kind of approval is required for such a change. So,
> > my
> > > suggestion would be that we have lazy majority within the next 24 hours
> > to
> > > create the repository, we proceed. Please let me know, if this
> requires a
> > > more formal approval.
> > >
> > > Best and thanks,
> > >
> > > Konstantin
> > >
> > > [1]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-42%3A+Rework+Flink+Documentation
> > > [2] https://issues.apache.org/jira/browse/FLINK-12749
> > >
> > >
> > > --
> > >
> > > Konstantin Knauf | Solutions Architect
> > >
> > > +49 160 91394525
> > >
> > >
> > > Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
> > >
> > >
> > > --
> > >
> > > Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> > >
> > > --
> > >
> > > Ververica GmbH
> > > Registered at Amtsgericht Charlottenburg: HRB 158244 B
> > > Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
> > >
> >
>

Re: [DISCUSS] Flink project bylaws

2019-07-11 Thread Aljoscha Krettek

Big +1

How different is this from the Kafka bylaws? I’m asking because I quite like 
them and wouldn’t mind essentially adopting the Kafka bylaws. I mean, it’s open 
source, and we don’t have to try to re-invent the wheel here.

I think it’s worthwhile to discuss the “committer +1” requirement. We don’t 
usually have that now but I would actually be in favour of requiring it, 
although it might make stuff more complicated.

Aljoscha

> On 11. Jul 2019, at 15:31, Till Rohrmann  wrote:
> 
> Thanks a lot for creating this draft Becket.
> 
> I think without the notion of emeritus (or active vs. inactive), it won't
> be possible to have a 2/3 majority vote because we already have too many
> inactive PMCs/committers.
> 
> For the case of a committer being the author and getting a +1 from a
> non-committer: I think a committer should know when to ask another
> committer for feedback or not. Hence, I would not enforce that we strictly
> need a +1 from a committer if the author is a committer but of course
> encourage it if capacities exist.
> 
> Cheers,
> Till
> 
> On Thu, Jul 11, 2019 at 3:08 PM Chesnay Schepler  wrote:
> 
>> The emeritus stuff seems like unnecessary noise.
>> 
>> There's a bunch of subtle changes in the draft compared to existing
>> "conventions"; we should find a way to highlight these and discuss them
>> one by one.
>> 
>> On 11/07/2019 14:29, Robert Metzger wrote:
>>> Thank you Becket for kicking off this discussion and creating a draft in
>>> the Wiki.
>>> 
>>> I left some comments in the wiki.
>>> 
>>> In my understanding this means, that a committer always needs a review
>> and
 +1 from another committer. As far as I know this is currently not always
 the case (often committer authors, contributor reviews & +1s).
>>> 
>>> I would agree to add such a bylaw, if we had cases in the past where code
>>> was not sufficiently reviewed AND we believe that we have enough capacity
>>> to ensure a separate committer's approval.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Thu, Jul 11, 2019 at 9:49 AM Konstantin Knauf <
>> konstan...@ververica.com>
>>> wrote:
>>> 
 Hi all,
 
 thanks a lot for driving this, Becket. I have two remarks regarding the
 "Actions" section:
 
 * In addition to a simple "Code Change" we could also add a row for
>> "Code
 Change requiring a FLIP" with a reference to the FLIP process page. A
>> FLIP
 will have/does have different rules for approvals, etc.
 * For "Code Change" the draft currently requires "one +1 from a
>> committer
 who has not authored the patch followed by a Lazy approval (not counting
 the vote of the contributor), moving to lazy majority if a -1 is
>> received".
 In my understanding this means, that a committer always needs a review
>> and
 +1 from another committer. As far as I know this is currently not always
 the case (often committer authors, contributor reviews & +1s).
 
 I think it is worth thinking about how we can make it easy to follow the
 bylaws e.g. by having more Flink-specific Jira workflows and ticket
>> types +
 corresponding permissions. While this is certainly "Step 2", I believe,
>> we
 really need to make it as easy & transparent as possible, otherwise they
 will be unintentionally broken.
 
 Cheers and thanks,
 
 Konstantin
 
 
 
 On Thu, Jul 11, 2019 at 9:10 AM Becket Qin 
>> wrote:
 
> Hi all,
> 
> As it was raised in the FLIP process discussion thread [1], currently
 Flink
> does not have official bylaws to govern the operation of the project.
 Such
> bylaws are critical for the community to coordinate and contribute
> together. It is also the basis of other processes such as FLIP.
> 
> I have drafted a Flink bylaws page and would like to start a discussion
> thread on this.
> 
 
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120731026
> The bylaws will affect everyone in the community. It'll be great to
>> hear
> your thoughts.
> 
> Thanks,
> 
> Jiangjie (Becket) Qin
> 
> [1]
> 
> 
 
>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-META-FLIP-Sticking-or-not-to-a-strict-FLIP-voting-process-td29978.html#none
 
 --
 
 Konstantin Knauf | Solutions Architect
 
 +49 160 91394525
 
 
 Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
 
 
 --
 
 Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
 
 --
 
 Ververica GmbH
 Registered at Amtsgericht Charlottenburg: HRB 158244 B
 Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
 
>> 
>>

Re: [DISCUSS] ARM support for Flink

2019-07-11 Thread Stephan Ewen

I think an ARM release would be cool.

To actually support that properly, we would need something like an ARM
profile for the CI builds (at least in the nightly tests), otherwise ARM
support would probably be broken frequently.
Maybe that could be a way to start? Create a Travis CI ARM build (if
possible) and see what tests pass and which parts of the system would need
to be adjusted?

On Thu, Jul 11, 2019 at 9:24 AM Xiyuan Wang 
wrote:

> Hi yun:
>   I didn't try to build rocksdb with vagrant, but just `make -j8
> rocksdbjava` directly in an ARM machine.  We hit some issues as well. My
> colleague has created an issue in rocksdb[1]. Rocksdb doesn't contains ARM
> .so file in his offical jar package. If you have the same request, let's
> work together there.
>
> Thanks.
>
> [1]: https://github.com/facebook/rocksdb/issues/5559
>
> Yun Tang  于2019年7月11日周四 下午12:01写道：
>
> > Hi Xiyuan
> >
> > Have you ever tried to release RocksDB on ARM like official doc[1]
> > suggests? From our experience, cross-building for ARM did not work fine
> > with Vagrant and we have to build rocksDB's binary file on ARM
> separately.
> >
> > As frocksdb [2] might not always maintained in Flink, I think we'd better
> > support to release RocksDB-java with ARM officially.
> >
> >
> > [1] https://github.com/facebook/rocksdb/blob/master/java/RELEASE.md
> > [2] https://github.com/dataArtisans/frocksdb
> >
> > Best
> > Yun Tang
> >
> >
> > 
> > From: Xiyuan Wang 
> > Sent: Tuesday, July 9, 2019 10:52
> > To: dev@flink.apache.org
> > Subject: Re: [DISCUSS] ARM support for Flink
> >
> > Thanks for your help. I built the frocksdb locally on ARM and all the
> > related tests are passed now. Except some tests which can be fixed
> easily,
> > it seems that both building and testing are ran well on ARM.
> >
> > Basing on my test, Is it possible to support Flink on ARM officailly?
> Seem
> > the worklist is not too long. And I can help with the CI testing part.
> >
> > Need Flink team's idea.
> >
> > Thanks.
> >
> > Dian Fu  于2019年7月8日周一 上午10:23写道：
> >
> > > Hi Xiyuan,
> > >
> > > Thanks for bring the discussion.
> > >
> > > WRT the exception, it's because the native bundled in the rocksdb jar
> > file
> > > isn't compiled with cross platform support. You can refer [1] for how
> to
> > > build rocksdb which has ARM platform.
> > >
> > > WRT ARM support, the rocksdb currently used in Flink is hosted in the
> > > Ververica git [2], so it won't be difficult to make it support ARM.
> > > However, I guess this git exists just for temporary [3], not because we
> > > want to add much feature in rocksdb.
> > >
> > > [1] https://github.com/facebook/rocksdb/issues/678 <
> > > https://github.com/facebook/rocksdb/issues/678>
> > > [2] https://github.com/dataArtisans/frocksdb <
> > > https://github.com/dataArtisans/frocksdb>
> > > [3] https://issues.apache.org/jira/browse/FLINK-10471 <
> > > https://issues.apache.org/jira/browse/FLINK-10471>
> > >
> > > Regards,
> > > Dian
> > >
> > > > 在 2019年7月8日，上午9:17，Xiyuan Wang  写道：
> > > >
> > > > Hi Flink:
> > > >  Recently we meet a problem that we have to test and run Flink on ARM
> > > > arch. While after searching Flink community, I didn’t find an
> official
> > > ARM
> > > > release version.
> > > >
> > > > Since Flink is made by Java and Scala language which can be ran
> > > > cross-platform usually, I think Flink can be built and ran on ARM
> > > directly
> > > > as well. Then with my local test, Flink was built and deployed
> success
> > as
> > > > expected. But some tests were failed due to ARM arch. For example:
> > > >
> > > > 1. MemoryArchitectureTest.testArchitectureNotUnknown:34 Values should
> > be
> > > > different. Actual: UNKNOWN
> > > > 2. [ERROR]
> > > >
> > >
> >
> testIterator(org.apache.flink.contrib.streaming.state.RocksDBRocksStateKeysIteratorTest)
> > > > Time elapsed: 0.234 s  <<< ERROR!
> > > > java.io.IOException: Could not load the native RocksDB library
> > > > at
> > > >
> > >
> >
> org.apache.flink.contrib.streaming.state.RocksDBRocksStateKeysIteratorTest.testIteratorHelper(RocksDBRocksStateKeysIteratorTest.java:90)
> > > > at
> > > >
> > >
> >
> org.apache.flink.contrib.streaming.state.RocksDBRocksStateKeysIteratorTest.testIterator(RocksDBRocksStateKeysIteratorTest.java:63)
> > > > Caused by: java.lang.UnsatisfiedLinkError:
> > > >
> > >
> >
> /tmp/rocksdb-lib-81ca7930b92af2cca143a050c0338d34/librocksdbjni-linux64.so:
> > > >
> > >
> >
> /tmp/rocksdb-lib-81ca7930b92af2cca143a050c0338d34/librocksdbjni-linux64.so:
> > > > cannot open shared object file: No such file or directory (Possible
> > > cause:
> > > > can't load AMD 64-bit .so on a AARCH64-bit platform)
> > > > …
> > > >
> > > >  Since the test isn’t passed totally, we are not sure if Flink 100%
> > > > support ARM or not. Is it possible for Flink to support ARM release
> > > > officially? I guess it may be not a very huge work basing on Java. I
> > > notice
> > > > that Flink now uses trivis-ci w

Re: [DISCUSS] Create "flink-playgrounds" repository

2019-07-11 Thread Konstantin Knauf

Hi Stephan,

putting it under "flink-quickstarts" alone would not help. The user would
still need to check out the whole `apache/flink` repository, which is a bit
overwhelming. The Java/Scala quickstarts use Maven archetypes. Is this what
you are suggesting? I think, this would be an option, but it seems strange
to manage a pure Docker setup (eventually maybe only one file) in a Maven
project.

Best,

Konstantin

On Thu, Jul 11, 2019 at 3:52 PM Stephan Ewen  wrote:

> Hi all!
>
> I am fine with a separate repository.
>
> Quick question. though: Have you considered putting the setup not under
> "docs" but under "flink-quickstart" or so?
> Would that be equally cumbersome for users?
>
> Best,
> Stephan
>
>
> On Thu, Jul 11, 2019 at 12:19 PM Fabian Hueske  wrote:
>
> > Hi,
> >
> > I think Quickstart should be as lightweight as possible and follow common
> > practices.
> > A Git repository for a few configuration files might feel like overkill,
> > but IMO it makes sense because this ensures users can get started with 3
> > commands:
> >
> > $ git clone .../flink-playground
> > $ cd flink-playground
> > $ docker-compose up -d
> >
> > So +1 to create a repository.
> >
> > Thanks, Fabian
> >
> > Am Do., 11. Juli 2019 um 12:07 Uhr schrieb Robert Metzger <
> > rmetz...@apache.org>:
> >
> > > +1 to create a repo.
> > >
> > > On Thu, Jul 11, 2019 at 11:10 AM Konstantin Knauf <
> > > konstan...@ververica.com>
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > in the course of implementing FLIP-42 we are currently reworking the
> > > > Getting Started section of our documentation. As part of this, we are
> > > > adding docker-compose-based playgrounds to get started with Flink
> > > > operations and Flink SQL quickly.
> > > >
> > > > To reduce as much friction as possible for new users, we would like
> to
> > > > maintain the required configuration files (docker-comose.yaml,
> > > > flink-conf.yaml) in a separate new repository,
> > > `apache/flink-playgrounds`.
> > > >
> > > > You can find more details and a brief discussion on this in the
> > > > corresponding Jira ticket [2].
> > > >
> > > > What do you think?
> > > >
> > > > I am not sure, what kind of approval is required for such a change.
> So,
> > > my
> > > > suggestion would be that we have lazy majority within the next 24
> hours
> > > to
> > > > create the repository, we proceed. Please let me know, if this
> > requires a
> > > > more formal approval.
> > > >
> > > > Best and thanks,
> > > >
> > > > Konstantin
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-42%3A+Rework+Flink+Documentation
> > > > [2] https://issues.apache.org/jira/browse/FLINK-12749
> > > >
> > > >
> > > > --
> > > >
> > > > Konstantin Knauf | Solutions Architect
> > > >
> > > > +49 160 91394525
> > > >
> > > >
> > > > Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
> > > >
> > > >
> > > > --
> > > >
> > > > Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> > > >
> > > > --
> > > >
> > > > Ververica GmbH
> > > > Registered at Amtsgericht Charlottenburg: HRB 158244 B
> > > > Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
> > > >
> > >
> >
>


-- 

Konstantin Knauf | Solutions Architect

+49 160 91394525


Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010


--

Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany

--

Ververica GmbH
Registered at Amtsgericht Charlottenburg: HRB 158244 B
Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen

[ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Fabian Hueske

Hi everyone,

I'm very happy to announce that Rong Rong accepted the offer of the Flink
PMC to become a committer of the Flink project.

Rong has been contributing to Flink for many years, mainly working on SQL
and Yarn security features. He's also frequently helping out on the
user@f.a.o mailing lists.

Congratulations Rong!

Best, Fabian
(on behalf of the Flink PMC)

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.9.0 release

Hi Chesnay,

Here is the JIRA list I have collected, all of them are under reviewing:

1. Hive UDF support (FLINK-13024, FLINK-13225)
2. Partition prune support (FLINK-13115)
3. Set StreamGraph properties in blink planner (FLINK-13121)
4. Support HBase upsert sink (FLINK-10245)
5. Support JDBC TableFactory (FLINK-13118)
6. Fix the bug of throwing IOException while FileBufferReader#nextBuffer
(FLINK-13110)
7. Bookkeeping of available resources of allocated slots in SlotPool
(FLINK-12765)
8. Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
(FLINK-13187)
9. Add support for batch slot requests to SlotPoolImpl (FLINK-13166)
10. Complete slot requests in request order (FLINK-13165)

Best,
Kurt


On Thu, Jul 11, 2019 at 6:12 PM Chesnay Schepler  wrote:

> Can we get JIRA's attached to these items so people out of the loop can
> track the progress?
>
> On 05/07/2019 16:06, Kurt Young wrote:
> > Here are the features I collected which are under actively developing and
> > close
> > to merge:
> >
> > 1. Bridge blink planner to unified table environment and remove
> TableConfig
> > from blink planner
> > 2. Support timestamp with local time zone and partition pruning in blink
> > planner
> > 3. Support JDBC & HBase lookup function and upsert sink
> > 4. StreamExecutionEnvironment supports executing job with StreamGraph,
> and
> > blink planner should set proper properties to StreamGraph
> > 5. Set resource profiles to task and enable managed memory as resource
> > profile
> >
> > Best,
> > Kurt
> >
> >
> > On Fri, Jul 5, 2019 at 9:37 PM Kurt Young  wrote:
> >
> >> Hi devs,
> >>
> >> It's July 5 now and we should announce feature freeze and cut the branch
> >> as planned. However, some components seems still not ready yet and
> >> various features are still under development or review.
> >>
> >> But we also can not extend the freeze day again which will further delay
> >> the
> >> release date. I think freeze new features today and have another couple
> >> of buffer days, letting features which are almost ready have a chance to
> >> get in is a reasonable solution.
> >>
> >> I hereby announce features of Flink 1.9.0 are freezed, *July 11* will be
> >> the
> >> day for cutting branch.  Since the feature freeze has effectively took
> >> place,
> >> I kindly ask committers to refrain from merging features that are
> planned
> >> for
> >> future releases into the master branch for the time being before the 1.9
> >> branch
> >> is cut. We understand this might be a bit inconvenient, thanks for the
> >> cooperation here.
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Fri, Jul 5, 2019 at 5:19 PM 罗齐  wrote:
> >>
> >>> Hi Gordon,
> >>>
> >>> Will branch 1.9 be cut out today? We're really looking forward to the
> >>> blink features in 1.9.
> >>>
> >>> Thanks,
> >>> Qi
> >>>
> >>> On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai <
> tzuli...@apache.org>
> >>> wrote:
> >>>
>  Thanks for the updates so far everyone!
> 
>  Since support for the new Blink-based Table / SQL runner and
> fine-grained
>  recovery are quite prominent features for 1.9.0,
>  and developers involved in these topics have already expressed that
> these
>  could make good use for another week,
>  I think it definitely makes sense to postpone the feature freeze.
> 
>  The new date for feature freeze and feature branch cut for 1.9.0 will
> be
>  *July
>  5*.
> 
>  Please update on this thread if there are any further concerns!
> 
>  Cheers,
>  Gordon
> 
>  On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler 
>  wrote:
> 
> > On the fine-grained recovery / batch scheduling side we could make
> good
> > use of another week.
> > Currently we are on track to have the _feature_ merged, but without
> > having done a great deal of end-to-end testing.
> >
> > On 25/06/2019 15:01, Kurt Young wrote:
> >> Hi Aljoscha,
> >>
> >> I also feel an additional week can make the remaining work more
>  easy. At
> >> least
> >> we don't have to check in lots of commits in both branches (master &
> >> release-1.9).
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Tue, Jun 25, 2019 at 8:27 PM Aljoscha Krettek <
>  aljos...@apache.org>
> >> wrote:
> >>
> >>> A few threads are converging around supporting the new Blink-based
>  Table
> >>> API Runner/Planner. I think hitting the currently proposed feature
> > freeze
> >>> date is hard, if not impossible, and that the work would benefit
>  from an
> >>> additional week to get everything in with good quality.
> >>>
> >>> What do the others involved in the topic think?
> >>>
> >>> Aljoscha
> >>>
>  On 24. Jun 2019, at 19:42, Bowen Li  wrote:
> 
>  Hi Gordon,
> 
>  Thanks for driving this effort.
> 
>  Xuefu responded to the discussion thread [1] and I want to brin

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Jark Wu

Congratulations Rong Rong!
Welcome on board!

On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:

> Hi everyone,
>
> I'm very happy to announce that Rong Rong accepted the offer of the Flink
> PMC to become a committer of the Flink project.
>
> Rong has been contributing to Flink for many years, mainly working on SQL
> and Yarn security features. He's also frequently helping out on the
> user@f.a.o mailing lists.
>
> Congratulations Rong!
>
> Best, Fabian
> (on behalf of the Flink PMC)
>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Kostas Kloudas

Congratulations Rong!

On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:

> Congratulations Rong Rong!
> Welcome on board!
>
> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
>
>> Hi everyone,
>>
>> I'm very happy to announce that Rong Rong accepted the offer of the Flink
>> PMC to become a committer of the Flink project.
>>
>> Rong has been contributing to Flink for many years, mainly working on SQL
>> and Yarn security features. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Rong!
>>
>> Best, Fabian
>> (on behalf of the Flink PMC)
>>
>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Shaoxuan Wang

 Congratulations Rong!

On Thu, Jul 11, 2019 at 10:40 PM Jark Wu  wrote:

> Congratulations Rong Rong!
> Welcome on board!
>
> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
>
>> Hi everyone,
>>
>> I'm very happy to announce that Rong Rong accepted the offer of the Flink
>> PMC to become a committer of the Flink project.
>>
>> Rong has been contributing to Flink for many years, mainly working on SQL
>> and Yarn security features. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Rong!
>>
>> Best, Fabian
>> (on behalf of the Flink PMC)
>>
>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

Congratulations Rong!

Best,
Kurt


On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas  wrote:

> Congratulations Rong!
>
> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
>
>> Congratulations Rong Rong!
>> Welcome on board!
>>
>> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
>>
>>> Hi everyone,
>>>
>>> I'm very happy to announce that Rong Rong accepted the offer of the
>>> Flink PMC to become a committer of the Flink project.
>>>
>>> Rong has been contributing to Flink for many years, mainly working on
>>> SQL and Yarn security features. He's also frequently helping out on the
>>> user@f.a.o mailing lists.
>>>
>>> Congratulations Rong!
>>>
>>> Best, Fabian
>>> (on behalf of the Flink PMC)
>>>
>>

[jira] [Created] (FLINK-13230) Retry acknowledgement calls

2019-07-11 Thread Richard Deurwaarder (JIRA)

Richard Deurwaarder created FLINK-13230:
---

 Summary: Retry acknowledgement calls
 Key: FLINK-13230
 URL: https://issues.apache.org/jira/browse/FLINK-13230
 Project: Flink
  Issue Type: Sub-task
  Components: Connectors / Google Cloud PubSub
Reporter: Richard Deurwaarder


Currently when a pubsub/grpc pull fails we retry based on configuration given 
by the user.

We should do the same for  Acknowledgement calls



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread zhijiang

Congratulations Rong!

Best,
Zhijiang
--
From:Kurt Young 
Send Time:2019年7月11日(星期四) 22:54
To:Kostas Kloudas 
Cc:Jark Wu ; Fabian Hueske ; dev 
; user 
Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer

Congratulations Rong!

Best,
Kurt

On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas  wrote:
Congratulations Rong!
On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
Congratulations Rong Rong! 
Welcome on board!
On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
Hi everyone,

I'm very happy to announce that Rong Rong accepted the offer of the Flink PMC 
to become a committer of the Flink project.

Rong has been contributing to Flink for many years, mainly working on SQL and 
Yarn security features. He's also frequently helping out on the user@f.a.o 
mailing lists.

Congratulations Rong!

Best, Fabian 
(on behalf of the Flink PMC)

[jira] [Created] (FLINK-13231) Add a ratelimiter to pubsub source

2019-07-11 Thread Richard Deurwaarder (JIRA)

Richard Deurwaarder created FLINK-13231:
---

 Summary: Add a ratelimiter to pubsub source
 Key: FLINK-13231
 URL: https://issues.apache.org/jira/browse/FLINK-13231
 Project: Flink
  Issue Type: Sub-task
  Components: Connectors / Google Cloud PubSub
Reporter: Richard Deurwaarder


Replace MaxMessagesToAcknowledge limit by introducing a rate limiter. See: 
[https://github.com/apache/flink/pull/6594#discussion_r300215868]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.9.0 release

2019-07-11 Thread Stephan Ewen

Number (6) is not a feature but a bug fix, so no need to block on that...

On Thu, Jul 11, 2019 at 4:27 PM Kurt Young  wrote:

> Hi Chesnay,
>
> Here is the JIRA list I have collected, all of them are under reviewing:
>
> 1. Hive UDF support (FLINK-13024, FLINK-13225)
> 2. Partition prune support (FLINK-13115)
> 3. Set StreamGraph properties in blink planner (FLINK-13121)
> 4. Support HBase upsert sink (FLINK-10245)
> 5. Support JDBC TableFactory (FLINK-13118)
> 6. Fix the bug of throwing IOException while FileBufferReader#nextBuffer
> (FLINK-13110)
> 7. Bookkeeping of available resources of allocated slots in SlotPool
> (FLINK-12765)
> 8. Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
> (FLINK-13187)
> 9. Add support for batch slot requests to SlotPoolImpl (FLINK-13166)
> 10. Complete slot requests in request order (FLINK-13165)
>
> Best,
> Kurt
>
>
> On Thu, Jul 11, 2019 at 6:12 PM Chesnay Schepler 
> wrote:
>
> > Can we get JIRA's attached to these items so people out of the loop can
> > track the progress?
> >
> > On 05/07/2019 16:06, Kurt Young wrote:
> > > Here are the features I collected which are under actively developing
> and
> > > close
> > > to merge:
> > >
> > > 1. Bridge blink planner to unified table environment and remove
> > TableConfig
> > > from blink planner
> > > 2. Support timestamp with local time zone and partition pruning in
> blink
> > > planner
> > > 3. Support JDBC & HBase lookup function and upsert sink
> > > 4. StreamExecutionEnvironment supports executing job with StreamGraph,
> > and
> > > blink planner should set proper properties to StreamGraph
> > > 5. Set resource profiles to task and enable managed memory as resource
> > > profile
> > >
> > > Best,
> > > Kurt
> > >
> > >
> > > On Fri, Jul 5, 2019 at 9:37 PM Kurt Young  wrote:
> > >
> > >> Hi devs,
> > >>
> > >> It's July 5 now and we should announce feature freeze and cut the
> branch
> > >> as planned. However, some components seems still not ready yet and
> > >> various features are still under development or review.
> > >>
> > >> But we also can not extend the freeze day again which will further
> delay
> > >> the
> > >> release date. I think freeze new features today and have another
> couple
> > >> of buffer days, letting features which are almost ready have a chance
> to
> > >> get in is a reasonable solution.
> > >>
> > >> I hereby announce features of Flink 1.9.0 are freezed, *July 11* will
> be
> > >> the
> > >> day for cutting branch.  Since the feature freeze has effectively took
> > >> place,
> > >> I kindly ask committers to refrain from merging features that are
> > planned
> > >> for
> > >> future releases into the master branch for the time being before the
> 1.9
> > >> branch
> > >> is cut. We understand this might be a bit inconvenient, thanks for the
> > >> cooperation here.
> > >>
> > >> Best,
> > >> Kurt
> > >>
> > >>
> > >> On Fri, Jul 5, 2019 at 5:19 PM 罗齐  wrote:
> > >>
> > >>> Hi Gordon,
> > >>>
> > >>> Will branch 1.9 be cut out today? We're really looking forward to the
> > >>> blink features in 1.9.
> > >>>
> > >>> Thanks,
> > >>> Qi
> > >>>
> > >>> On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai <
> > tzuli...@apache.org>
> > >>> wrote:
> > >>>
> >  Thanks for the updates so far everyone!
> > 
> >  Since support for the new Blink-based Table / SQL runner and
> > fine-grained
> >  recovery are quite prominent features for 1.9.0,
> >  and developers involved in these topics have already expressed that
> > these
> >  could make good use for another week,
> >  I think it definitely makes sense to postpone the feature freeze.
> > 
> >  The new date for feature freeze and feature branch cut for 1.9.0
> will
> > be
> >  *July
> >  5*.
> > 
> >  Please update on this thread if there are any further concerns!
> > 
> >  Cheers,
> >  Gordon
> > 
> >  On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler <
> ches...@apache.org>
> >  wrote:
> > 
> > > On the fine-grained recovery / batch scheduling side we could make
> > good
> > > use of another week.
> > > Currently we are on track to have the _feature_ merged, but without
> > > having done a great deal of end-to-end testing.
> > >
> > > On 25/06/2019 15:01, Kurt Young wrote:
> > >> Hi Aljoscha,
> > >>
> > >> I also feel an additional week can make the remaining work more
> >  easy. At
> > >> least
> > >> we don't have to check in lots of commits in both branches
> (master &
> > >> release-1.9).
> > >>
> > >> Best,
> > >> Kurt
> > >>
> > >>
> > >> On Tue, Jun 25, 2019 at 8:27 PM Aljoscha Krettek <
> >  aljos...@apache.org>
> > >> wrote:
> > >>
> > >>> A few threads are converging around supporting the new
> Blink-based
> >  Table
> > >>> API Runner/Planner. I think hitting the currently proposed
> feature
> > > freeze
> > >>> date is hard, if not imp

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Yu Li

Congratulations Rong!

Best Regards,
Yu


On Thu, 11 Jul 2019 at 22:54, zhijiang  wrote:

> Congratulations Rong!
>
> Best,
> Zhijiang
>
> --
> From:Kurt Young 
> Send Time:2019年7月11日(星期四) 22:54
> To:Kostas Kloudas 
> Cc:Jark Wu ; Fabian Hueske ; dev <
> dev@flink.apache.org>; user 
> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>
> Congratulations Rong!
>
> Best,
> Kurt
>
>
> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
> wrote:
> Congratulations Rong!
>
> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
> Congratulations Rong Rong!
> Welcome on board!
>
> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
> Hi everyone,
>
> I'm very happy to announce that Rong Rong accepted the offer of the Flink
> PMC to become a committer of the Flink project.
>
> Rong has been contributing to Flink for many years, mainly working on SQL
> and Yarn security features. He's also frequently helping out on the
> user@f.a.o mailing lists.
>
> Congratulations Rong!
>
> Best, Fabian
> (on behalf of the Flink PMC)
>
>
>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Shuyi Chen

Congratulations, Rong!

On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:

> Congratulations Rong!
>
> Best Regards,
> Yu
>
>
> On Thu, 11 Jul 2019 at 22:54, zhijiang  wrote:
>
>> Congratulations Rong!
>>
>> Best,
>> Zhijiang
>>
>> --
>> From:Kurt Young 
>> Send Time:2019年7月11日(星期四) 22:54
>> To:Kostas Kloudas 
>> Cc:Jark Wu ; Fabian Hueske ; dev <
>> dev@flink.apache.org>; user 
>> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>>
>> Congratulations Rong!
>>
>> Best,
>> Kurt
>>
>>
>> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
>> wrote:
>> Congratulations Rong!
>>
>> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
>> Congratulations Rong Rong!
>> Welcome on board!
>>
>> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
>> Hi everyone,
>>
>> I'm very happy to announce that Rong Rong accepted the offer of the Flink
>> PMC to become a committer of the Flink project.
>>
>> Rong has been contributing to Flink for many years, mainly working on SQL
>> and Yarn security features. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Rong!
>>
>> Best, Fabian
>> (on behalf of the Flink PMC)
>>
>>
>>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Xingcan Cui

Congrats Rong!

Best,
Xingcan

> On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:
> 
> Congratulations, Rong!
> 
> On Thu, Jul 11, 2019 at 8:26 AM Yu Li  > wrote:
> Congratulations Rong!
> 
> Best Regards,
> Yu
> 
> 
> On Thu, 11 Jul 2019 at 22:54, zhijiang  > wrote:
> Congratulations Rong!
> 
> Best,
> Zhijiang
> --
> From:Kurt Young mailto:ykt...@gmail.com>>
> Send Time:2019年7月11日(星期四) 22:54
> To:Kostas Kloudas mailto:kklou...@gmail.com>>
> Cc:Jark Wu mailto:imj...@gmail.com>>; Fabian Hueske 
> mailto:fhue...@gmail.com>>; dev  >; user  >
> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
> 
> Congratulations Rong!
> 
> Best,
> Kurt
> 
> 
> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas  > wrote:
> Congratulations Rong!
> 
> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  > wrote:
> Congratulations Rong Rong! 
> Welcome on board!
> 
> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  > wrote:
> Hi everyone,
> 
> I'm very happy to announce that Rong Rong accepted the offer of the Flink PMC 
> to become a committer of the Flink project.
> 
> Rong has been contributing to Flink for many years, mainly working on SQL and 
> Yarn security features. He's also frequently helping out on the user@f.a.o 
> mailing lists.
> 
> Congratulations Rong!
> 
> Best, Fabian 
> (on behalf of the Flink PMC)
>

Re: [DISCUSS] Flink project bylaws

2019-07-11 Thread Becket Qin

Thanks everyone for all the comments and feedback. Please see the replies
below:

Re: Konstantin

> * In addition to a simple "Code Change" we could also add a row for "Code
> Change requiring a FLIP" with a reference to the FLIP process page. A FLIP
> will have/does have different rules for approvals, etc.

Good point. Just added the entry.

---
Re: Konstantin

> * For "Code Change" the draft currently requires "one +1 from a committer
> who has not authored the patch followed by a Lazy approval (not counting
> the vote of the contributor), moving to lazy majority if a -1 is received".
> In my understanding this means, that a committer always needs a review and
> +1 from another committer. As far as I know this is currently not always
> the case (often committer authors, contributor reviews & +1s).
>

I think it is worth thinking about how we can make it easy to follow the
> bylaws e.g. by having more Flink-specific Jira workflows and ticket types +
> corresponding permissions. While this is certainly "Step 2", I believe, we
> really need to make it as easy & transparent as possible, otherwise they
> will be unintentionally broken.

& Re: Till

> For the case of a committer being the author and getting a +1 from a
> non-committer: I think a committer should know when to ask another
> committer for feedback or not. Hence, I would not enforce that we strictly
> need a +1 from a committer if the author is a committer but of course
> encourage it if capacities exist.

I am with Robert and Aljoscha on this.

I completely understand the concern here. TBH, in Kafka occasionally
trivial patches from committers are still merged without following the
cross-review requirement, but it is rare. That said, I still think an
additional committer's review makes sense due to the following reasons:
1. The bottom line here is that we need to make sure every patch is
reviewed with a high quality. This is a little difficult to guarantee if
the review comes from a contributor for many reasons. In some cases, a
contributor may not have enough knowledge about the project to make a good
judgement. Also sometimes the contributors are more eagerly to get a
particular issue fixed, so they are willing to lower the review bar.
2. One byproduct of such cross review among committers, which I personally
feel useful, is that it helps gradually form consistent design principles
and code style. This is because the committers will know how the other
committers are writing code and learn from each other. So they tend to
reach some tacit understanding on how things should be done in general.

Another way to think about this is to consider the following two scenarios:
1. Reviewing a committer's patch takes a lot of iterations. Then the patch
needs to be reviewed even if it takes time because there are things
actually needs to be clarified / changed.
2. Reviewing a committer's patch is very smooth and quick, so the patch is
merged soon. Then reviewing such a patch does not take much time.

Letting another committer review the patch from a committer falls either in
case 1 or case 2. The best option here is to review the patch because
If it is case 1, the patch actually needs to be reviewed.
If it is case 2, the review should not take much time anyways.

In the contrast, we will risk encounter case 1 if we skip the cross-review.

Re: Robert

I replied to your comments in the wiki and made the following modifications
to resolve some of your comments:
1. Added a release manager role section.
2. changed the name of "lazy consensus" to "consensus" to align with
general definition of Apache glossary and other projects.
3. review board  -> pull request

-
Re: Chesnay

The emeritus stuff seems like unnecessary noise.
>
As Till mentioned, this is to make sure 2/3 majority is still feasible in
practice.

There's a bunch of subtle changes in the draft compared to existing
> "conventions"; we should find a way to highlight these and discuss them
> one by one.

That is a good suggestion. I am not familiar enough with the current Flink
convention. Will you help on this? I saw you commented on some part in the
wiki. Are those complete?

--
 Re: Aljoscha

How different is this from the Kafka bylaws? I’m asking because I quite
> like them and wouldn’t mind essentially adopting the Kafka bylaws. I mean,
> it’s open source, and we don’t have to try to re-invent the wheel here.

Ha, you got me on this. The first version of the draft was almost identical
to Kafka. But Robert has already caught a few inconsistent places. So it
might still worth going through it to make sure we truly agree on them.
Otherwise we may end up modifying them shortly after adoption.

Thanks again folks, for all the valuable feedback. These are great
discussion.

Jiangjie (Becket) Qin

On Thu, Jul 11, 2019 at 9:55 PM Aljoscha Krettek 
wrote:

> Big +1
>
> H

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Becket Qin

Congrats, Rong!

On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui  wrote:

> Congrats Rong!
>
> Best,
> Xingcan
>
> On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:
>
> Congratulations, Rong!
>
> On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:
>
>> Congratulations Rong!
>>
>> Best Regards,
>> Yu
>>
>>
>> On Thu, 11 Jul 2019 at 22:54, zhijiang 
>> wrote:
>>
>>> Congratulations Rong!
>>>
>>> Best,
>>> Zhijiang
>>>
>>> --
>>> From:Kurt Young 
>>> Send Time:2019年7月11日(星期四) 22:54
>>> To:Kostas Kloudas 
>>> Cc:Jark Wu ; Fabian Hueske ; dev <
>>> dev@flink.apache.org>; user 
>>> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>>>
>>> Congratulations Rong!
>>>
>>> Best,
>>> Kurt
>>>
>>>
>>> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
>>> wrote:
>>> Congratulations Rong!
>>>
>>> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
>>> Congratulations Rong Rong!
>>> Welcome on board!
>>>
>>> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
>>> Hi everyone,
>>>
>>> I'm very happy to announce that Rong Rong accepted the offer of the
>>> Flink PMC to become a committer of the Flink project.
>>>
>>> Rong has been contributing to Flink for many years, mainly working on
>>> SQL and Yarn security features. He's also frequently helping out on the
>>> user@f.a.o mailing lists.
>>>
>>> Congratulations Rong!
>>>
>>> Best, Fabian
>>> (on behalf of the Flink PMC)
>>>
>>>
>>>
>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Peter Huang

Congrats Rong!

On Thu, Jul 11, 2019 at 10:40 AM Becket Qin  wrote:

> Congrats, Rong!
>
> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui  wrote:
>
>> Congrats Rong!
>>
>> Best,
>> Xingcan
>>
>> On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:
>>
>> Congratulations, Rong!
>>
>> On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:
>>
>>> Congratulations Rong!
>>>
>>> Best Regards,
>>> Yu
>>>
>>>
>>> On Thu, 11 Jul 2019 at 22:54, zhijiang 
>>> wrote:
>>>
 Congratulations Rong!

 Best,
 Zhijiang

 --
 From:Kurt Young 
 Send Time:2019年7月11日(星期四) 22:54
 To:Kostas Kloudas 
 Cc:Jark Wu ; Fabian Hueske ; dev <
 dev@flink.apache.org>; user 
 Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer

 Congratulations Rong!

 Best,
 Kurt

 On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
 wrote:
 Congratulations Rong!

 On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
 Congratulations Rong Rong!
 Welcome on board!

 On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  wrote:
 Hi everyone,

 I'm very happy to announce that Rong Rong accepted the offer of the
 Flink PMC to become a committer of the Flink project.

 Rong has been contributing to Flink for many years, mainly working on
 SQL and Yarn security features. He's also frequently helping out on the
 user@f.a.o mailing lists.

 Congratulations Rong!

 Best, Fabian
 (on behalf of the Flink PMC)

>>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Bowen Li

Congrats, Rong!


On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  wrote:

> Congratulations Rong!
>
> ---
> Oytun Tez
>
> *M O T A W O R D*
> The World's Fastest Human Translation Platform.
> oy...@motaword.com — www.motaword.com
>
>
> On Thu, Jul 11, 2019 at 1:44 PM Peter Huang 
> wrote:
>
>> Congrats Rong!
>>
>> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin  wrote:
>>
>>> Congrats, Rong!
>>>
>>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui  wrote:
>>>
 Congrats Rong!

 Best,
 Xingcan

 On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:

 Congratulations, Rong!

 On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:

> Congratulations Rong!
>
> Best Regards,
> Yu
>
>
> On Thu, 11 Jul 2019 at 22:54, zhijiang 
> wrote:
>
>> Congratulations Rong!
>>
>> Best,
>> Zhijiang
>>
>> --
>> From:Kurt Young 
>> Send Time:2019年7月11日(星期四) 22:54
>> To:Kostas Kloudas 
>> Cc:Jark Wu ; Fabian Hueske ;
>> dev ; user 
>> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>>
>> Congratulations Rong!
>>
>> Best,
>> Kurt
>>
>>
>> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
>> wrote:
>> Congratulations Rong!
>>
>> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
>> Congratulations Rong Rong!
>> Welcome on board!
>>
>> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
>> wrote:
>> Hi everyone,
>>
>> I'm very happy to announce that Rong Rong accepted the offer of the
>> Flink PMC to become a committer of the Flink project.
>>
>> Rong has been contributing to Flink for many years, mainly working on
>> SQL and Yarn security features. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Rong!
>>
>> Best, Fabian
>> (on behalf of the Flink PMC)
>>
>>
>>

Re: [DISCUSS] Flink project bylaws

2019-07-11 Thread Bowen Li

On Thu, Jul 11, 2019 at 10:38 AM Becket Qin  wrote:

> Thanks everyone for all the comments and feedback. Please see the replies
> below:
>
> 
> Re: Konstantin
>
> > * In addition to a simple "Code Change" we could also add a row for "Code
> > Change requiring a FLIP" with a reference to the FLIP process page. A
> FLIP
> > will have/does have different rules for approvals, etc.
>
>
> Good point. Just added the entry.
>
> ---
> Re: Konstantin
>
> > * For "Code Change" the draft currently requires "one +1 from a committer
> > who has not authored the patch followed by a Lazy approval (not counting
> > the vote of the contributor), moving to lazy majority if a -1 is
> received".
> > In my understanding this means, that a committer always needs a review
> and
> > +1 from another committer. As far as I know this is currently not always
> > the case (often committer authors, contributor reviews & +1s).
> >
>
>
> I think it is worth thinking about how we can make it easy to follow the
> > bylaws e.g. by having more Flink-specific Jira workflows and ticket
> types +
> > corresponding permissions. While this is certainly "Step 2", I believe,
> we
> > really need to make it as easy & transparent as possible, otherwise they
> > will be unintentionally broken.
>
>
> & Re: Till
>
> > For the case of a committer being the author and getting a +1 from a
> > non-committer: I think a committer should know when to ask another
> > committer for feedback or not. Hence, I would not enforce that we
> strictly
> > need a +1 from a committer if the author is a committer but of course
> > encourage it if capacities exist.
>
>
> I am with Robert and Aljoscha on this.
>
> I completely understand the concern here. TBH, in Kafka occasionally
> trivial patches from committers are still merged without following the
> cross-review requirement, but it is rare. That said, I still think an
> additional committer's review makes sense due to the following reasons:
> 1. The bottom line here is that we need to make sure every patch is
> reviewed with a high quality. This is a little difficult to guarantee if
> the review comes from a contributor for many reasons. In some cases, a
> contributor may not have enough knowledge about the project to make a good
> judgement. Also sometimes the contributors are more eagerly to get a
> particular issue fixed, so they are willing to lower the review bar.
> 2. One byproduct of such cross review among committers, which I personally
> feel useful, is that it helps gradually form consistent design principles
> and code style. This is because the committers will know how the other
> committers are writing code and learn from each other. So they tend to
> reach some tacit understanding on how things should be done in general.
>
> Another way to think about this is to consider the following two scenarios:
> 1. Reviewing a committer's patch takes a lot of iterations. Then the patch
> needs to be reviewed even if it takes time because there are things
> actually needs to be clarified / changed.
> 2. Reviewing a committer's patch is very smooth and quick, so the patch is
> merged soon. Then reviewing such a patch does not take much time.
>
> Letting another committer review the patch from a committer falls either in
> case 1 or case 2. The best option here is to review the patch because
> If it is case 1, the patch actually needs to be reviewed.
> If it is case 2, the review should not take much time anyways.
>
> In the contrast, we will risk encounter case 1 if we skip the cross-review.
>
> 
> Re: Robert
>
> I replied to your comments in the wiki and made the following modifications
> to resolve some of your comments:
> 1. Added a release manager role section.
> 2. changed the name of "lazy consensus" to "consensus" to align with
> general definition of Apache glossary and other projects.
> 3. review board  -> pull request
>
> -
> Re: Chesnay
>
> The emeritus stuff seems like unnecessary noise.
> >
> As Till mentioned, this is to make sure 2/3 majority is still feasible in
> practice.
>
> There's a bunch of subtle changes in the draft compared to existing
> > "conventions"; we should find a way to highlight these and discuss them
> > one by one.
>
> That is a good suggestion. I am not familiar enough with the current Flink
> convention. Will you help on this? I saw you commented on some part in the
> wiki. Are those complete?
>
> --
>  Re: Aljoscha
>
> How different is this from the Kafka bylaws? I’m asking because I quite
> > like them and wouldn’t mind essentially adopting the Kafka bylaws. I
> mean,
> > it’s open source, and we don’t have to try to re-invent the wheel here.
>
> Ha, you got me on this. The first version of the draft was almost identical
> to Kafka. But Robert has already caught a few inconsistent places. So it
> might still worth going through it to make sure we tr

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Xuefu Z

Congratulations, Rong!

On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  wrote:

> Congrats, Rong!
>
>
> On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  wrote:
>
> > Congratulations Rong!
> >
> > ---
> > Oytun Tez
> >
> > *M O T A W O R D*
> > The World's Fastest Human Translation Platform.
> > oy...@motaword.com — www.motaword.com
> >
> >
> > On Thu, Jul 11, 2019 at 1:44 PM Peter Huang 
> > wrote:
> >
> >> Congrats Rong!
> >>
> >> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin 
> wrote:
> >>
> >>> Congrats, Rong!
> >>>
> >>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui 
> wrote:
> >>>
>  Congrats Rong!
> 
>  Best,
>  Xingcan
> 
>  On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:
> 
>  Congratulations, Rong!
> 
>  On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:
> 
> > Congratulations Rong!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Thu, 11 Jul 2019 at 22:54, zhijiang 
> > wrote:
> >
> >> Congratulations Rong!
> >>
> >> Best,
> >> Zhijiang
> >>
> >> --
> >> From:Kurt Young 
> >> Send Time:2019年7月11日(星期四) 22:54
> >> To:Kostas Kloudas 
> >> Cc:Jark Wu ; Fabian Hueske ;
> >> dev ; user 
> >> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
> >>
> >> Congratulations Rong!
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas  >
> >> wrote:
> >> Congratulations Rong!
> >>
> >> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
> >> Congratulations Rong Rong!
> >> Welcome on board!
> >>
> >> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
> >> wrote:
> >> Hi everyone,
> >>
> >> I'm very happy to announce that Rong Rong accepted the offer of the
> >> Flink PMC to become a committer of the Flink project.
> >>
> >> Rong has been contributing to Flink for many years, mainly working
> on
> >> SQL and Yarn security features. He's also frequently helping out on
> the
> >> user@f.a.o mailing lists.
> >>
> >> Congratulations Rong!
> >>
> >> Best, Fabian
> >> (on behalf of the Flink PMC)
> >>
> >>
> >>
> 
>


-- 
Xuefu Zhang

"In Honey We Trust!"

Re: [DISCUSS] Create "flink-playgrounds" repository

2019-07-11 Thread Xuefu Z

The idea seems interesting, but I'm wondering if we have considered
publishing .tz file hosted somewhere in Flink site with a link in the doc.
This might avoid the "overkill" of introducing a repo, which is main used
for version control in development cycles. On the other hand, a docker
setup, once published, will seldom (if ever) go thru revisions.

Thanks,
Xuefu



On Thu, Jul 11, 2019 at 6:58 AM Konstantin Knauf 
wrote:

> Hi Stephan,
>
> putting it under "flink-quickstarts" alone would not help. The user would
> still need to check out the whole `apache/flink` repository, which is a bit
> overwhelming. The Java/Scala quickstarts use Maven archetypes. Is this what
> you are suggesting? I think, this would be an option, but it seems strange
> to manage a pure Docker setup (eventually maybe only one file) in a Maven
> project.
>
> Best,
>
> Konstantin
>
> On Thu, Jul 11, 2019 at 3:52 PM Stephan Ewen  wrote:
>
> > Hi all!
> >
> > I am fine with a separate repository.
> >
> > Quick question. though: Have you considered putting the setup not under
> > "docs" but under "flink-quickstart" or so?
> > Would that be equally cumbersome for users?
> >
> > Best,
> > Stephan
> >
> >
> > On Thu, Jul 11, 2019 at 12:19 PM Fabian Hueske 
> wrote:
> >
> > > Hi,
> > >
> > > I think Quickstart should be as lightweight as possible and follow
> common
> > > practices.
> > > A Git repository for a few configuration files might feel like
> overkill,
> > > but IMO it makes sense because this ensures users can get started with
> 3
> > > commands:
> > >
> > > $ git clone .../flink-playground
> > > $ cd flink-playground
> > > $ docker-compose up -d
> > >
> > > So +1 to create a repository.
> > >
> > > Thanks, Fabian
> > >
> > > Am Do., 11. Juli 2019 um 12:07 Uhr schrieb Robert Metzger <
> > > rmetz...@apache.org>:
> > >
> > > > +1 to create a repo.
> > > >
> > > > On Thu, Jul 11, 2019 at 11:10 AM Konstantin Knauf <
> > > > konstan...@ververica.com>
> > > > wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > in the course of implementing FLIP-42 we are currently reworking
> the
> > > > > Getting Started section of our documentation. As part of this, we
> are
> > > > > adding docker-compose-based playgrounds to get started with Flink
> > > > > operations and Flink SQL quickly.
> > > > >
> > > > > To reduce as much friction as possible for new users, we would like
> > to
> > > > > maintain the required configuration files (docker-comose.yaml,
> > > > > flink-conf.yaml) in a separate new repository,
> > > > `apache/flink-playgrounds`.
> > > > >
> > > > > You can find more details and a brief discussion on this in the
> > > > > corresponding Jira ticket [2].
> > > > >
> > > > > What do you think?
> > > > >
> > > > > I am not sure, what kind of approval is required for such a change.
> > So,
> > > > my
> > > > > suggestion would be that we have lazy majority within the next 24
> > hours
> > > > to
> > > > > create the repository, we proceed. Please let me know, if this
> > > requires a
> > > > > more formal approval.
> > > > >
> > > > > Best and thanks,
> > > > >
> > > > > Konstantin
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-42%3A+Rework+Flink+Documentation
> > > > > [2] https://issues.apache.org/jira/browse/FLINK-12749
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Konstantin Knauf | Solutions Architect
> > > > >
> > > > > +49 160 91394525
> > > > >
> > > > >
> > > > > Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> > > > >
> > > > > --
> > > > >
> > > > > Ververica GmbH
> > > > > Registered at Amtsgericht Charlottenburg: HRB 158244 B
> > > > > Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
> > > > >
> > > >
> > >
> >
>
>
> --
>
> Konstantin Knauf | Solutions Architect
>
> +49 160 91394525
>
>
> Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2010
>
>
> --
>
> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
>
> --
>
> Ververica GmbH
> Registered at Amtsgericht Charlottenburg: HRB 158244 B
> Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
>


-- 
Xuefu Zhang

"In Honey We Trust!"

[jira] [Created] (FLINK-13232) TemporalTypesTest>ExpressionTestBase.evaluateExprs fails on PST Timezone

2019-07-11 Thread Bowen Li (JIRA)

Bowen Li created FLINK-13232:


 Summary: TemporalTypesTest>ExpressionTestBase.evaluateExprs fails 
on PST Timezone
 Key: FLINK-13232
 URL: https://issues.apache.org/jira/browse/FLINK-13232
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Planner
Affects Versions: 1.9.0
Reporter: Bowen Li
Assignee: Jingsong Lee
 Fix For: 1.9.0


TemporalTypesTest>ExpressionTestBase.evaluateExprs seems to have a bug on 
timezone.

When I run it locally at PST timezone, it always fails as:

{code:java}
[ERROR] Failures:
[ERROR]   TemporalTypesTest>ExpressionTestBase.evaluateExprs:154 Wrong result 
for: [CURRENT_DATE] optimized to: [CURRENT_DATE] expected:<2019-07-1[2]> but 
was:<2019-07-1[1]>
{code}

I didn't find it fails on travis. Thus I suspect there's a bug w.r.t. timezone.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Hao Sun

Congratulations Rong.

On Thu, Jul 11, 2019, 11:39 Xuefu Z  wrote:

> Congratulations, Rong!
>
> On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  wrote:
>
>> Congrats, Rong!
>>
>>
>> On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  wrote:
>>
>> > Congratulations Rong!
>> >
>> > ---
>> > Oytun Tez
>> >
>> > *M O T A W O R D*
>> > The World's Fastest Human Translation Platform.
>> > oy...@motaword.com — www.motaword.com
>> 
>> >
>> >
>> > On Thu, Jul 11, 2019 at 1:44 PM Peter Huang > >
>> > wrote:
>> >
>> >> Congrats Rong!
>> >>
>> >> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin 
>> wrote:
>> >>
>> >>> Congrats, Rong!
>> >>>
>> >>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui 
>> wrote:
>> >>>
>>  Congrats Rong!
>> 
>>  Best,
>>  Xingcan
>> 
>>  On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:
>> 
>>  Congratulations, Rong!
>> 
>>  On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:
>> 
>> > Congratulations Rong!
>> >
>> > Best Regards,
>> > Yu
>> >
>> >
>> > On Thu, 11 Jul 2019 at 22:54, zhijiang 
>> > wrote:
>> >
>> >> Congratulations Rong!
>> >>
>> >> Best,
>> >> Zhijiang
>> >>
>> >> --
>> >> From:Kurt Young 
>> >> Send Time:2019年7月11日(星期四) 22:54
>> >> To:Kostas Kloudas 
>> >> Cc:Jark Wu ; Fabian Hueske ;
>> >> dev ; user 
>> >> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>> >>
>> >> Congratulations Rong!
>> >>
>> >> Best,
>> >> Kurt
>> >>
>> >>
>> >> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas <
>> kklou...@gmail.com>
>> >> wrote:
>> >> Congratulations Rong!
>> >>
>> >> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
>> >> Congratulations Rong Rong!
>> >> Welcome on board!
>> >>
>> >> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
>> >> wrote:
>> >> Hi everyone,
>> >>
>> >> I'm very happy to announce that Rong Rong accepted the offer of the
>> >> Flink PMC to become a committer of the Flink project.
>> >>
>> >> Rong has been contributing to Flink for many years, mainly working
>> on
>> >> SQL and Yarn security features. He's also frequently helping out
>> on the
>> >> user@f.a.o mailing lists.
>> >>
>> >> Congratulations Rong!
>> >>
>> >> Best, Fabian
>> >> (on behalf of the Flink PMC)
>> >>
>> >>
>> >>
>> 
>>
>
>
> --
> Xuefu Zhang
>
> "In Honey We Trust!"
>

[jira] [Created] (FLINK-13233) add end-to-end tests for "USE CATALOG" and "USE DATABASE" commands in SQL CLI

2019-07-11 Thread Bowen Li (JIRA)

Bowen Li created FLINK-13233:


 Summary: add end-to-end tests for "USE CATALOG" and "USE DATABASE" 
commands in SQL CLI
 Key: FLINK-13233
 URL: https://issues.apache.org/jira/browse/FLINK-13233
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / Client
Reporter: Bowen Li
Assignee: Bowen Li
 Fix For: 1.9.0






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Rong Rong

Thank you all for the warm welcome!

It's my honor to become an Apache Flink committer.
I will continue to work on this great project and contribute more to the
community.

Cheers,
Rong

On Thu, Jul 11, 2019 at 1:05 PM Hao Sun  wrote:

> Congratulations Rong.
>
> On Thu, Jul 11, 2019, 11:39 Xuefu Z  wrote:
>
>> Congratulations, Rong!
>>
>> On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  wrote:
>>
>>> Congrats, Rong!
>>>
>>>
>>> On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  wrote:
>>>
>>> > Congratulations Rong!
>>> >
>>> > ---
>>> > Oytun Tez
>>> >
>>> > *M O T A W O R D*
>>> > The World's Fastest Human Translation Platform.
>>> > oy...@motaword.com — www.motaword.com
>>> >
>>> >
>>> > On Thu, Jul 11, 2019 at 1:44 PM Peter Huang <
>>> huangzhenqiu0...@gmail.com>
>>> > wrote:
>>> >
>>> >> Congrats Rong!
>>> >>
>>> >> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin 
>>> wrote:
>>> >>
>>> >>> Congrats, Rong!
>>> >>>
>>> >>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui 
>>> wrote:
>>> >>>
>>>  Congrats Rong!
>>> 
>>>  Best,
>>>  Xingcan
>>> 
>>>  On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:
>>> 
>>>  Congratulations, Rong!
>>> 
>>>  On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:
>>> 
>>> > Congratulations Rong!
>>> >
>>> > Best Regards,
>>> > Yu
>>> >
>>> >
>>> > On Thu, 11 Jul 2019 at 22:54, zhijiang >> >
>>> > wrote:
>>> >
>>> >> Congratulations Rong!
>>> >>
>>> >> Best,
>>> >> Zhijiang
>>> >>
>>> >> --
>>> >> From:Kurt Young 
>>> >> Send Time:2019年7月11日(星期四) 22:54
>>> >> To:Kostas Kloudas 
>>> >> Cc:Jark Wu ; Fabian Hueske ;
>>> >> dev ; user 
>>> >> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>>> >>
>>> >> Congratulations Rong!
>>> >>
>>> >> Best,
>>> >> Kurt
>>> >>
>>> >>
>>> >> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas <
>>> kklou...@gmail.com>
>>> >> wrote:
>>> >> Congratulations Rong!
>>> >>
>>> >> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
>>> >> Congratulations Rong Rong!
>>> >> Welcome on board!
>>> >>
>>> >> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
>>> >> wrote:
>>> >> Hi everyone,
>>> >>
>>> >> I'm very happy to announce that Rong Rong accepted the offer of
>>> the
>>> >> Flink PMC to become a committer of the Flink project.
>>> >>
>>> >> Rong has been contributing to Flink for many years, mainly
>>> working on
>>> >> SQL and Yarn security features. He's also frequently helping out
>>> on the
>>> >> user@f.a.o mailing lists.
>>> >>
>>> >> Congratulations Rong!
>>> >>
>>> >> Best, Fabian
>>> >> (on behalf of the Flink PMC)
>>> >>
>>> >>
>>> >>
>>> 
>>>
>>
>>
>> --
>> Xuefu Zhang
>>
>> "In Honey We Trust!"
>>
>

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Chen YuZhao

congratulations!

获取 Outlook for iOS


发件人: Rong Rong 
发送时间: 星期五, 七月 12, 2019 8:09 上午
收件人: Hao Sun
抄送: Xuefu Z; dev; Flink ML
主题: Re: [ANNOUNCE] Rong Rong becomes a Flink committer

Thank you all for the warm welcome!

It's my honor to become an Apache Flink committer.
I will continue to work on this great project and contribute more to the 
community.

Cheers,
Rong

On Thu, Jul 11, 2019 at 1:05 PM Hao Sun 
mailto:ha...@zendesk.com>> wrote:
Congratulations Rong.

On Thu, Jul 11, 2019, 11:39 Xuefu Z 
mailto:usxu...@gmail.com>> wrote:
Congratulations, Rong!

On Thu, Jul 11, 2019 at 10:59 AM Bowen Li 
mailto:bowenl...@gmail.com>> wrote:
Congrats, Rong!


On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez 
mailto:oy...@motaword.com>> wrote:

> Congratulations Rong!
>
> ---
> Oytun Tez
>
> *M O T A W O R D*
> The World's Fastest Human Translation Platform.
> oy...@motaword.com ― 
> www.motaword.com
>
>
> On Thu, Jul 11, 2019 at 1:44 PM Peter Huang 
> mailto:huangzhenqiu0...@gmail.com>>
> wrote:
>
>> Congrats Rong!
>>
>> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin 
>> mailto:becket@gmail.com>> wrote:
>>
>>> Congrats, Rong!
>>>
>>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui 
>>> mailto:xingc...@gmail.com>> wrote:
>>>
 Congrats Rong!

 Best,
 Xingcan

 On Jul 11, 2019, at 1:08 PM, Shuyi Chen 
 mailto:suez1...@gmail.com>> wrote:

 Congratulations, Rong!

 On Thu, Jul 11, 2019 at 8:26 AM Yu Li 
 mailto:car...@gmail.com>> wrote:

> Congratulations Rong!
>
> Best Regards,
> Yu
>
>
> On Thu, 11 Jul 2019 at 22:54, zhijiang 
> mailto:wangzhijiang...@aliyun.com>>
> wrote:
>
>> Congratulations Rong!
>>
>> Best,
>> Zhijiang
>>
>> --
>> From:Kurt Young mailto:ykt...@gmail.com>>
>> Send Time:2019年7月11日(星期四) 22:54
>> To:Kostas Kloudas mailto:kklou...@gmail.com>>
>> Cc:Jark Wu mailto:imj...@gmail.com>>; Fabian Hueske 
>> mailto:fhue...@gmail.com>>;
>> dev mailto:dev@flink.apache.org>>; user 
>> mailto:u...@flink.apache.org>>
>> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>>
>> Congratulations Rong!
>>
>> Best,
>> Kurt
>>
>>
>> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
>> mailto:kklou...@gmail.com>>
>> wrote:
>> Congratulations Rong!
>>
>> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu 
>> mailto:imj...@gmail.com>> wrote:
>> Congratulations Rong Rong!
>> Welcome on board!
>>
>> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
>> mailto:fhue...@gmail.com>>
>> wrote:
>> Hi everyone,
>>
>> I'm very happy to announce that Rong Rong accepted the offer of the
>> Flink PMC to become a committer of the Flink project.
>>
>> Rong has been contributing to Flink for many years, mainly working on
>> SQL and Yarn security features. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Rong!
>>
>> Best, Fabian
>> (on behalf of the Flink PMC)
>>
>>
>>



--
Xuefu Zhang

"In Honey We Trust!"

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Dian Fu


Congrats Rong!


> 在 2019年7月12日，上午8:47，Chen YuZhao  写道：
> 
> congratulations!
> 
> 获取 Outlook for iOS 
>  
> 发件人: Rong Rong 
> 发送时间: 星期五, 七月 12, 2019 8:09 上午
> 收件人: Hao Sun
> 抄送: Xuefu Z; dev; Flink ML
> 主题: Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>  
> Thank you all for the warm welcome!
> 
> It's my honor to become an Apache Flink committer. 
> I will continue to work on this great project and contribute more to the 
> community.
> 
> Cheers,
> Rong
> 
> On Thu, Jul 11, 2019 at 1:05 PM Hao Sun  > wrote:
> Congratulations Rong. 
> 
> On Thu, Jul 11, 2019, 11:39 Xuefu Z  > wrote:
> Congratulations, Rong!
> 
> On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  > wrote:
> Congrats, Rong!
> 
> 
> On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  > wrote:
> 
> > Congratulations Rong!
> >
> > ---
> > Oytun Tez
> >
> > *M O T A W O R D*
> > The World's Fastest Human Translation Platform.
> > oy...@motaword.com  ― www.motaword.com 
> > 
> >
> >
> > On Thu, Jul 11, 2019 at 1:44 PM Peter Huang  > >
> > wrote:
> >
> >> Congrats Rong!
> >>
> >> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin  >> > wrote:
> >>
> >>> Congrats, Rong!
> >>>
> >>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui  >>> > wrote:
> >>>
>  Congrats Rong!
> 
>  Best,
>  Xingcan
> 
>  On Jul 11, 2019, at 1:08 PM, Shuyi Chen   > wrote:
> 
>  Congratulations, Rong!
> 
>  On Thu, Jul 11, 2019 at 8:26 AM Yu Li   > wrote:
> 
> > Congratulations Rong!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Thu, 11 Jul 2019 at 22:54, zhijiang  > >
> > wrote:
> >
> >> Congratulations Rong!
> >>
> >> Best,
> >> Zhijiang
> >>
> >> --
> >> From:Kurt Young mailto:ykt...@gmail.com>>
> >> Send Time:2019年7月11日(星期四) 22:54
> >> To:Kostas Kloudas mailto:kklou...@gmail.com>>
> >> Cc:Jark Wu mailto:imj...@gmail.com>>; Fabian Hueske 
> >> mailto:fhue...@gmail.com>>;
> >> dev mailto:dev@flink.apache.org>>; user 
> >> mailto:u...@flink.apache.org>>
> >> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
> >>
> >> Congratulations Rong!
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas  >> >
> >> wrote:
> >> Congratulations Rong!
> >>
> >> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  >> > wrote:
> >> Congratulations Rong Rong!
> >> Welcome on board!
> >>
> >> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  >> >
> >> wrote:
> >> Hi everyone,
> >>
> >> I'm very happy to announce that Rong Rong accepted the offer of the
> >> Flink PMC to become a committer of the Flink project.
> >>
> >> Rong has been contributing to Flink for many years, mainly working on
> >> SQL and Yarn security features. He's also frequently helping out on the
> >> user@f.a.o mailing lists.
> >>
> >> Congratulations Rong!
> >>
> >> Best, Fabian
> >> (on behalf of the Flink PMC)
> >>
> >>
> >>
> 
> 
> 
> -- 
> Xuefu Zhang
> 
> "In Honey We Trust!"

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread jincheng sun

Congratulations Rong, Well deserved!

Cheers,
Jincheng

Dian Fu  于2019年7月12日周五 上午9:06写道：

>
> Congrats Rong!
>
>
> 在 2019年7月12日，上午8:47，Chen YuZhao  写道：
>
> congratulations!
>
> 获取 Outlook for iOS 
>
> --
> *发件人:* Rong Rong 
> *发送时间:* 星期五, 七月 12, 2019 8:09 上午
> *收件人:* Hao Sun
> *抄送:* Xuefu Z; dev; Flink ML
> *主题:* Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>
> Thank you all for the warm welcome!
>
> It's my honor to become an Apache Flink committer.
> I will continue to work on this great project and contribute more to the
> community.
>
> Cheers,
> Rong
>
> On Thu, Jul 11, 2019 at 1:05 PM Hao Sun  wrote:
>
>> Congratulations Rong.
>>
>> On Thu, Jul 11, 2019, 11:39 Xuefu Z  wrote:
>>
>>> Congratulations, Rong!
>>>
>>> On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  wrote:
>>>
 Congrats, Rong!


 On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  wrote:

 > Congratulations Rong!
 >
 > ---
 > Oytun Tez
 >
 > *M O T A W O R D*
 > The World's Fastest Human Translation Platform.
 > oy...@motaword.com — www.motaword.com
 >
 >
 > On Thu, Jul 11, 2019 at 1:44 PM Peter Huang <
 huangzhenqiu0...@gmail.com>
 > wrote:
 >
 >> Congrats Rong!
 >>
 >> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin 
 wrote:
 >>
 >>> Congrats, Rong!
 >>>
 >>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui 
 wrote:
 >>>
  Congrats Rong!
 
  Best,
  Xingcan
 
  On Jul 11, 2019, at 1:08 PM, Shuyi Chen 
 wrote:
 
  Congratulations, Rong!
 
  On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:
 
 > Congratulations Rong!
 >
 > Best Regards,
 > Yu
 >
 >
 > On Thu, 11 Jul 2019 at 22:54, zhijiang <
 wangzhijiang...@aliyun.com>
 > wrote:
 >
 >> Congratulations Rong!
 >>
 >> Best,
 >> Zhijiang
 >>
 >>
 --
 >> From:Kurt Young 
 >> Send Time:2019年7月11日(星期四) 22:54
 >> To:Kostas Kloudas 
 >> Cc:Jark Wu ; Fabian Hueske >>> >;
 >> dev ; user 
 >> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
 >>
 >> Congratulations Rong!
 >>
 >> Best,
 >> Kurt
 >>
 >>
 >> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas <
 kklou...@gmail.com>
 >> wrote:
 >> Congratulations Rong!
 >>
 >> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu 
 wrote:
 >> Congratulations Rong Rong!
 >> Welcome on board!
 >>
 >> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
 >> wrote:
 >> Hi everyone,
 >>
 >> I'm very happy to announce that Rong Rong accepted the offer of
 the
 >> Flink PMC to become a committer of the Flink project.
 >>
 >> Rong has been contributing to Flink for many years, mainly
 working on
 >> SQL and Yarn security features. He's also frequently helping out
 on the
 >> user@f.a.o mailing lists.
 >>
 >> Congratulations Rong!
 >>
 >> Best, Fabian
 >> (on behalf of the Flink PMC)
 >>
 >>
 >>
 

>>>
>>>
>>> --
>>> Xuefu Zhang
>>>
>>> "In Honey We Trust!"
>>>
>>
>

[jira] [Created] (FLINK-13234) TemporalTypesTest randomly failed on travis

Kurt Young created FLINK-13234:
--

 Summary: TemporalTypesTest randomly failed on travis
 Key: FLINK-13234
 URL: https://issues.apache.org/jira/browse/FLINK-13234
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Planner
Affects Versions: 1.9.0
Reporter: Kurt Young
Assignee: Jingsong Lee


TemporalTypesTest>ExpressionTestBase.evaluateExprs:154 Wrong result for: 
[CURRENT_DATE] optimized to: [CURRENT_DATE] expected:<2019-07-1[2]> but 
was:<2019-07-1[1]>

 

more details in: [https://api.travis-ci.org/v3/job/557582157/log.txt]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread JingsongLee

Congratulations Rong. 
Rong Rong has done a lot of nice work in the past time to the flink community.

Best, JingsongLee


--
From:Rong Rong 
Send Time:2019年7月12日(星期五) 08:09
To:Hao Sun 
Cc:Xuefu Z ; dev ; Flink ML 

Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer

Thank you all for the warm welcome!

It's my honor to become an Apache Flink committer. 
I will continue to work on this great project and contribute more to the 
community.

Cheers,
Rong
On Thu, Jul 11, 2019 at 1:05 PM Hao Sun  wrote:

Congratulations Rong. 
On Thu, Jul 11, 2019, 11:39 Xuefu Z  wrote:
Congratulations, Rong!

On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  wrote:
Congrats, Rong!


 On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  wrote:

 > Congratulations Rong!
 >
 > ---
 > Oytun Tez
 >
 > *M O T A W O R D*
 > The World's Fastest Human Translation Platform.
 > oy...@motaword.com — www.motaword.com
 >
 >
 > On Thu, Jul 11, 2019 at 1:44 PM Peter Huang 
 > wrote:
 >
 >> Congrats Rong!
 >>
 >> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin  wrote:
 >>
 >>> Congrats, Rong!
 >>>
 >>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui  wrote:
 >>>
  Congrats Rong!
 
  Best,
  Xingcan
 
  On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:
 
  Congratulations, Rong!
 
  On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:
 
 > Congratulations Rong!
 >
 > Best Regards,
 > Yu
 >
 >
 > On Thu, 11 Jul 2019 at 22:54, zhijiang 
 > wrote:
 >
 >> Congratulations Rong!
 >>
 >> Best,
 >> Zhijiang
 >>
 >> --
 >> From:Kurt Young 
 >> Send Time:2019年7月11日(星期四) 22:54
 >> To:Kostas Kloudas 
 >> Cc:Jark Wu ; Fabian Hueske ;
 >> dev ; user 
 >> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
 >>
 >> Congratulations Rong!
 >>
 >> Best,
 >> Kurt
 >>
 >>
 >> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
 >> wrote:
 >> Congratulations Rong!
 >>
 >> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
 >> Congratulations Rong Rong!
 >> Welcome on board!
 >>
 >> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
 >> wrote:
 >> Hi everyone,
 >>
 >> I'm very happy to announce that Rong Rong accepted the offer of the
 >> Flink PMC to become a committer of the Flink project.
 >>
 >> Rong has been contributing to Flink for many years, mainly working on
 >> SQL and Yarn security features. He's also frequently helping out on the
 >> user@f.a.o mailing lists.
 >>
 >> Congratulations Rong!
 >>
 >> Best, Fabian
 >> (on behalf of the Flink PMC)
 >>
 >>
 >>
 


-- 
Xuefu Zhang

"In Honey We Trust!"

Re:Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Haibo Sun

Congrats Rong!Best,
Haibo

At 2019-07-12 09:40:26, "JingsongLee"  wrote:

Congratulations Rong. 
Rong Rong has done a lot of nice work in the past time to the flink community.


Best, JingsongLee


--
From:Rong Rong 
Send Time:2019年7月12日(星期五) 08:09
To:Hao Sun 
Cc:Xuefu Z ; dev ; Flink ML 

Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer


Thank you all for the warm welcome!


It's my honor to become an Apache Flink committer. 
I will continue to work on this great project and contribute more to the 
community.



Cheers,
Rong


On Thu, Jul 11, 2019 at 1:05 PM Hao Sun  wrote:

Congratulations Rong. 


On Thu, Jul 11, 2019, 11:39 Xuefu Z  wrote:

Congratulations, Rong!



On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  wrote:

Congrats, Rong!


On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  wrote:

> Congratulations Rong!
>
> ---
> Oytun Tez
>
> *M O T A W O R D*
> The World's Fastest Human Translation Platform.
> oy...@motaword.com — www.motaword.com
>
>
> On Thu, Jul 11, 2019 at 1:44 PM Peter Huang 
> wrote:
>
>> Congrats Rong!
>>
>> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin  wrote:
>>
>>> Congrats, Rong!
>>>
>>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui  wrote:
>>>
 Congrats Rong!

 Best,
 Xingcan

 On Jul 11, 2019, at 1:08 PM, Shuyi Chen  wrote:

 Congratulations, Rong!

 On Thu, Jul 11, 2019 at 8:26 AM Yu Li  wrote:

> Congratulations Rong!
>
> Best Regards,
> Yu
>
>
> On Thu, 11 Jul 2019 at 22:54, zhijiang 
> wrote:
>
>> Congratulations Rong!
>>
>> Best,
>> Zhijiang
>>
>> --
>> From:Kurt Young 
>> Send Time:2019年7月11日(星期四) 22:54
>> To:Kostas Kloudas 
>> Cc:Jark Wu ; Fabian Hueske ;
>> dev ; user 
>> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
>>
>> Congratulations Rong!
>>
>> Best,
>> Kurt
>>
>>
>> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas 
>> wrote:
>> Congratulations Rong!
>>
>> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  wrote:
>> Congratulations Rong Rong!
>> Welcome on board!
>>
>> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske 
>> wrote:
>> Hi everyone,
>>
>> I'm very happy to announce that Rong Rong accepted the offer of the
>> Flink PMC to become a committer of the Flink project.
>>
>> Rong has been contributing to Flink for many years, mainly working on
>> SQL and Yarn security features. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Rong!
>>
>> Best, Fabian
>> (on behalf of the Flink PMC)
>>
>>
>>




--

Xuefu Zhang

"In Honey We Trust!"

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread 袁智翔

Congratulations, Rong!

> On Jul 11, 2019, at 22:24, Fabian Hueske  wrote:
> 
> Hi everyone,
> 
> I'm very happy to announce that Rong Rong accepted the offer of the Flink
> PMC to become a committer of the Flink project.
> 
> Rong has been contributing to Flink for many years, mainly working on SQL
> and Yarn security features. He's also frequently helping out on the
> user@f.a.o mailing lists.
> 
> Congratulations Rong!
> 
> Best, Fabian
> (on behalf of the Flink PMC)

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Paul Lam

Congrats to Rong! Rong has contributed a lot to the community and well deserves 
it.

Best,
Paul Lam

> 在 2019年7月12日，09:40，JingsongLee  写道：
> 
> Congratulations Rong. 
> Rong Rong has done a lot of nice work in the past time to the flink community.
> 
> Best, JingsongLee
> 
> --
> From:Rong Rong 
> Send Time:2019年7月12日(星期五) 08:09
> To:Hao Sun 
> Cc:Xuefu Z ; dev ; Flink ML 
> 
> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
> 
> Thank you all for the warm welcome!
> 
> It's my honor to become an Apache Flink committer. 
> I will continue to work on this great project and contribute more to the 
> community.
> 
> Cheers,
> Rong
> 
> On Thu, Jul 11, 2019 at 1:05 PM Hao Sun  > wrote:
> Congratulations Rong. 
> 
> On Thu, Jul 11, 2019, 11:39 Xuefu Z  > wrote:
> Congratulations, Rong!
> 
> On Thu, Jul 11, 2019 at 10:59 AM Bowen Li  > wrote:
> Congrats, Rong!
> 
> 
> On Thu, Jul 11, 2019 at 10:48 AM Oytun Tez  > wrote:
> 
> > Congratulations Rong!
> >
> > ---
> > Oytun Tez
> >
> > *M O T A W O R D*
> > The World's Fastest Human Translation Platform.
> > oy...@motaword.com  — www.motaword.com 
> > 
> >
> >
> > On Thu, Jul 11, 2019 at 1:44 PM Peter Huang  > >
> > wrote:
> >
> >> Congrats Rong!
> >>
> >> On Thu, Jul 11, 2019 at 10:40 AM Becket Qin  >> > wrote:
> >>
> >>> Congrats, Rong!
> >>>
> >>> On Fri, Jul 12, 2019 at 1:13 AM Xingcan Cui  >>> > wrote:
> >>>
>  Congrats Rong!
> 
>  Best,
>  Xingcan
> 
>  On Jul 11, 2019, at 1:08 PM, Shuyi Chen   > wrote:
> 
>  Congratulations, Rong!
> 
>  On Thu, Jul 11, 2019 at 8:26 AM Yu Li   > wrote:
> 
> > Congratulations Rong!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Thu, 11 Jul 2019 at 22:54, zhijiang  > >
> > wrote:
> >
> >> Congratulations Rong!
> >>
> >> Best,
> >> Zhijiang
> >>
> >> --
> >> From:Kurt Young mailto:ykt...@gmail.com>>
> >> Send Time:2019年7月11日(星期四) 22:54
> >> To:Kostas Kloudas mailto:kklou...@gmail.com>>
> >> Cc:Jark Wu mailto:imj...@gmail.com>>; Fabian Hueske 
> >> mailto:fhue...@gmail.com>>;
> >> dev mailto:dev@flink.apache.org>>; user 
> >> mailto:u...@flink.apache.org>>
> >> Subject:Re: [ANNOUNCE] Rong Rong becomes a Flink committer
> >>
> >> Congratulations Rong!
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Thu, Jul 11, 2019 at 10:53 PM Kostas Kloudas  >> >
> >> wrote:
> >> Congratulations Rong!
> >>
> >> On Thu, Jul 11, 2019 at 4:40 PM Jark Wu  >> > wrote:
> >> Congratulations Rong Rong!
> >> Welcome on board!
> >>
> >> On Thu, 11 Jul 2019 at 22:25, Fabian Hueske  >> >
> >> wrote:
> >> Hi everyone,
> >>
> >> I'm very happy to announce that Rong Rong accepted the offer of the
> >> Flink PMC to become a committer of the Flink project.
> >>
> >> Rong has been contributing to Flink for many years, mainly working on
> >> SQL and Yarn security features. He's also frequently helping out on the
> >> user@f.a.o mailing lists.
> >>
> >> Congratulations Rong!
> >>
> >> Best, Fabian
> >> (on behalf of the Flink PMC)
> >>
> >>
> >>
> 
> 
> 
> -- 
> Xuefu Zhang
> 
> "In Honey We Trust!"

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread vino yang

congratulations Rong Rong!

Fabian Hueske  于2019年7月11日周四 下午10:25写道：

> Hi everyone,
>
> I'm very happy to announce that Rong Rong accepted the offer of the Flink
> PMC to become a committer of the Flink project.
>
> Rong has been contributing to Flink for many years, mainly working on SQL
> and Yarn security features. He's also frequently helping out on the
> user@f.a.o mailing lists.
>
> Congratulations Rong!
>
> Best, Fabian
> (on behalf of the Flink PMC)
>

Apply for being a contributor

2019-07-11 Thread hongton122

Hi all,


I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is XD122, my fullname is Xiang Dong.






Tanks very much;

Re: [DISCUSS] ARM support for Flink

2019-07-11 Thread Xiyuan Wang

Hi Stephan
  yeah, we should add an ARM CI first. But Travis CI doesn't support ARM
arch itself. OpenLab community support it. As I mentioned before, OpenLab
is an opensource CI system like travis-ci.[1], it uses opensource CI
project `zuul`[2] for its deployment. Now some opensource project has
intergreted with it already. For example, `contained` project from
CNCF community[3]. And I have a POC for Flink ARM build and test using
OpenLab. Now the build is passed[4], and I'm working on debugging with the
`test` part[5]. Is it fine for Flink to using?

[1]: https://openlabtesting.org
[2]: https://zuul-ci.org/docs/zuul/
[3]: https://status.openlabtesting.org/projects
[4]:
https://status.openlabtesting.org/build/2aa33f1a87854679b70f36bd6f75a890
[5]: https://github.com/theopenlab/flink/pull/1


Stephan Ewen  于2019年7月11日周四 下午9:56写道：

> I think an ARM release would be cool.
>
> To actually support that properly, we would need something like an ARM
> profile for the CI builds (at least in the nightly tests), otherwise ARM
> support would probably be broken frequently.
> Maybe that could be a way to start? Create a Travis CI ARM build (if
> possible) and see what tests pass and which parts of the system would need
> to be adjusted?
>
> On Thu, Jul 11, 2019 at 9:24 AM Xiyuan Wang 
> wrote:
>
> > Hi yun:
> >   I didn't try to build rocksdb with vagrant, but just `make -j8
> > rocksdbjava` directly in an ARM machine.  We hit some issues as well. My
> > colleague has created an issue in rocksdb[1]. Rocksdb doesn't contains
> ARM
> > .so file in his offical jar package. If you have the same request, let's
> > work together there.
> >
> > Thanks.
> >
> > [1]: https://github.com/facebook/rocksdb/issues/5559
> >
> > Yun Tang  于2019年7月11日周四 下午12:01写道：
> >
> > > Hi Xiyuan
> > >
> > > Have you ever tried to release RocksDB on ARM like official doc[1]
> > > suggests? From our experience, cross-building for ARM did not work fine
> > > with Vagrant and we have to build rocksDB's binary file on ARM
> > separately.
> > >
> > > As frocksdb [2] might not always maintained in Flink, I think we'd
> better
> > > support to release RocksDB-java with ARM officially.
> > >
> > >
> > > [1] https://github.com/facebook/rocksdb/blob/master/java/RELEASE.md
> > > [2] https://github.com/dataArtisans/frocksdb
> > >
> > > Best
> > > Yun Tang
> > >
> > >
> > > 
> > > From: Xiyuan Wang 
> > > Sent: Tuesday, July 9, 2019 10:52
> > > To: dev@flink.apache.org
> > > Subject: Re: [DISCUSS] ARM support for Flink
> > >
> > > Thanks for your help. I built the frocksdb locally on ARM and all the
> > > related tests are passed now. Except some tests which can be fixed
> > easily,
> > > it seems that both building and testing are ran well on ARM.
> > >
> > > Basing on my test, Is it possible to support Flink on ARM officailly?
> > Seem
> > > the worklist is not too long. And I can help with the CI testing part.
> > >
> > > Need Flink team's idea.
> > >
> > > Thanks.
> > >
> > > Dian Fu  于2019年7月8日周一 上午10:23写道：
> > >
> > > > Hi Xiyuan,
> > > >
> > > > Thanks for bring the discussion.
> > > >
> > > > WRT the exception, it's because the native bundled in the rocksdb jar
> > > file
> > > > isn't compiled with cross platform support. You can refer [1] for how
> > to
> > > > build rocksdb which has ARM platform.
> > > >
> > > > WRT ARM support, the rocksdb currently used in Flink is hosted in the
> > > > Ververica git [2], so it won't be difficult to make it support ARM.
> > > > However, I guess this git exists just for temporary [3], not because
> we
> > > > want to add much feature in rocksdb.
> > > >
> > > > [1] https://github.com/facebook/rocksdb/issues/678 <
> > > > https://github.com/facebook/rocksdb/issues/678>
> > > > [2] https://github.com/dataArtisans/frocksdb <
> > > > https://github.com/dataArtisans/frocksdb>
> > > > [3] https://issues.apache.org/jira/browse/FLINK-10471 <
> > > > https://issues.apache.org/jira/browse/FLINK-10471>
> > > >
> > > > Regards,
> > > > Dian
> > > >
> > > > > 在 2019年7月8日，上午9:17，Xiyuan Wang  写道：
> > > > >
> > > > > Hi Flink:
> > > > >  Recently we meet a problem that we have to test and run Flink on
> ARM
> > > > > arch. While after searching Flink community, I didn’t find an
> > official
> > > > ARM
> > > > > release version.
> > > > >
> > > > > Since Flink is made by Java and Scala language which can be ran
> > > > > cross-platform usually, I think Flink can be built and ran on ARM
> > > > directly
> > > > > as well. Then with my local test, Flink was built and deployed
> > success
> > > as
> > > > > expected. But some tests were failed due to ARM arch. For example:
> > > > >
> > > > > 1. MemoryArchitectureTest.testArchitectureNotUnknown:34 Values
> should
> > > be
> > > > > different. Actual: UNKNOWN
> > > > > 2. [ERROR]
> > > > >
> > > >
> > >
> >
> testIterator(org.apache.flink.contrib.streaming.state.RocksDBRocksStateKeysIteratorTest)
> > > > > Time elapsed: 0.234 s  <<< ERROR!
> > > > > jav

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.9.0 release

2019-07-11 Thread qi luo

Any news on this?

Thanks,
Qi

> On Jul 11, 2019, at 11:13 PM, Stephan Ewen  wrote:
> 
> Number (6) is not a feature but a bug fix, so no need to block on that...
> 
> On Thu, Jul 11, 2019 at 4:27 PM Kurt Young  wrote:
> 
>> Hi Chesnay,
>> 
>> Here is the JIRA list I have collected, all of them are under reviewing:
>> 
>> 1. Hive UDF support (FLINK-13024, FLINK-13225)
>> 2. Partition prune support (FLINK-13115)
>> 3. Set StreamGraph properties in blink planner (FLINK-13121)
>> 4. Support HBase upsert sink (FLINK-10245)
>> 5. Support JDBC TableFactory (FLINK-13118)
>> 6. Fix the bug of throwing IOException while FileBufferReader#nextBuffer
>> (FLINK-13110)
>> 7. Bookkeeping of available resources of allocated slots in SlotPool
>> (FLINK-12765)
>> 8. Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
>> (FLINK-13187)
>> 9. Add support for batch slot requests to SlotPoolImpl (FLINK-13166)
>> 10. Complete slot requests in request order (FLINK-13165)
>> 
>> Best,
>> Kurt
>> 
>> 
>> On Thu, Jul 11, 2019 at 6:12 PM Chesnay Schepler 
>> wrote:
>> 
>>> Can we get JIRA's attached to these items so people out of the loop can
>>> track the progress?
>>> 
>>> On 05/07/2019 16:06, Kurt Young wrote:
 Here are the features I collected which are under actively developing
>> and
 close
 to merge:
 
 1. Bridge blink planner to unified table environment and remove
>>> TableConfig
 from blink planner
 2. Support timestamp with local time zone and partition pruning in
>> blink
 planner
 3. Support JDBC & HBase lookup function and upsert sink
 4. StreamExecutionEnvironment supports executing job with StreamGraph,
>>> and
 blink planner should set proper properties to StreamGraph
 5. Set resource profiles to task and enable managed memory as resource
 profile
 
 Best,
 Kurt
 
 
 On Fri, Jul 5, 2019 at 9:37 PM Kurt Young  wrote:
 
> Hi devs,
> 
> It's July 5 now and we should announce feature freeze and cut the
>> branch
> as planned. However, some components seems still not ready yet and
> various features are still under development or review.
> 
> But we also can not extend the freeze day again which will further
>> delay
> the
> release date. I think freeze new features today and have another
>> couple
> of buffer days, letting features which are almost ready have a chance
>> to
> get in is a reasonable solution.
> 
> I hereby announce features of Flink 1.9.0 are freezed, *July 11* will
>> be
> the
> day for cutting branch.  Since the feature freeze has effectively took
> place,
> I kindly ask committers to refrain from merging features that are
>>> planned
> for
> future releases into the master branch for the time being before the
>> 1.9
> branch
> is cut. We understand this might be a bit inconvenient, thanks for the
> cooperation here.
> 
> Best,
> Kurt
> 
> 
> On Fri, Jul 5, 2019 at 5:19 PM 罗齐  wrote:
> 
>> Hi Gordon,
>> 
>> Will branch 1.9 be cut out today? We're really looking forward to the
>> blink features in 1.9.
>> 
>> Thanks,
>> Qi
>> 
>> On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai <
>>> tzuli...@apache.org>
>> wrote:
>> 
>>> Thanks for the updates so far everyone!
>>> 
>>> Since support for the new Blink-based Table / SQL runner and
>>> fine-grained
>>> recovery are quite prominent features for 1.9.0,
>>> and developers involved in these topics have already expressed that
>>> these
>>> could make good use for another week,
>>> I think it definitely makes sense to postpone the feature freeze.
>>> 
>>> The new date for feature freeze and feature branch cut for 1.9.0
>> will
>>> be
>>> *July
>>> 5*.
>>> 
>>> Please update on this thread if there are any further concerns!
>>> 
>>> Cheers,
>>> Gordon
>>> 
>>> On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler <
>> ches...@apache.org>
>>> wrote:
>>> 
 On the fine-grained recovery / batch scheduling side we could make
>>> good
 use of another week.
 Currently we are on track to have the _feature_ merged, but without
 having done a great deal of end-to-end testing.
 
 On 25/06/2019 15:01, Kurt Young wrote:
> Hi Aljoscha,
> 
> I also feel an additional week can make the remaining work more
>>> easy. At
> least
> we don't have to check in lots of commits in both branches
>> (master &
> release-1.9).
> 
> Best,
> Kurt
> 
> 
> On Tue, Jun 25, 2019 at 8:27 PM Aljoscha Krettek <
>>> aljos...@apache.org>
> wrote:
> 
>> A few threads are converging around supporting the new
>> Blink-based
>>> Table
>> API Runner/Planner. I think hitting the currently proposed
>

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.9.0 release

2019-07-11 Thread qi luo

Do we have a new timeline for 1.9 branch cut?

Thanks,
Qi

> On Jul 12, 2019, at 11:42 AM, qi luo  wrote:
> 
> Any news on this?
> 
> Thanks,
> Qi
> 
>> On Jul 11, 2019, at 11:13 PM, Stephan Ewen  wrote:
>> 
>> Number (6) is not a feature but a bug fix, so no need to block on that...
>> 
>> On Thu, Jul 11, 2019 at 4:27 PM Kurt Young  wrote:
>> 
>>> Hi Chesnay,
>>> 
>>> Here is the JIRA list I have collected, all of them are under reviewing:
>>> 
>>> 1. Hive UDF support (FLINK-13024, FLINK-13225)
>>> 2. Partition prune support (FLINK-13115)
>>> 3. Set StreamGraph properties in blink planner (FLINK-13121)
>>> 4. Support HBase upsert sink (FLINK-10245)
>>> 5. Support JDBC TableFactory (FLINK-13118)
>>> 6. Fix the bug of throwing IOException while FileBufferReader#nextBuffer
>>> (FLINK-13110)
>>> 7. Bookkeeping of available resources of allocated slots in SlotPool
>>> (FLINK-12765)
>>> 8. Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
>>> (FLINK-13187)
>>> 9. Add support for batch slot requests to SlotPoolImpl (FLINK-13166)
>>> 10. Complete slot requests in request order (FLINK-13165)
>>> 
>>> Best,
>>> Kurt
>>> 
>>> 
>>> On Thu, Jul 11, 2019 at 6:12 PM Chesnay Schepler 
>>> wrote:
>>> 
 Can we get JIRA's attached to these items so people out of the loop can
 track the progress?
 
 On 05/07/2019 16:06, Kurt Young wrote:
> Here are the features I collected which are under actively developing
>>> and
> close
> to merge:
> 
> 1. Bridge blink planner to unified table environment and remove
 TableConfig
> from blink planner
> 2. Support timestamp with local time zone and partition pruning in
>>> blink
> planner
> 3. Support JDBC & HBase lookup function and upsert sink
> 4. StreamExecutionEnvironment supports executing job with StreamGraph,
 and
> blink planner should set proper properties to StreamGraph
> 5. Set resource profiles to task and enable managed memory as resource
> profile
> 
> Best,
> Kurt
> 
> 
> On Fri, Jul 5, 2019 at 9:37 PM Kurt Young  wrote:
> 
>> Hi devs,
>> 
>> It's July 5 now and we should announce feature freeze and cut the
>>> branch
>> as planned. However, some components seems still not ready yet and
>> various features are still under development or review.
>> 
>> But we also can not extend the freeze day again which will further
>>> delay
>> the
>> release date. I think freeze new features today and have another
>>> couple
>> of buffer days, letting features which are almost ready have a chance
>>> to
>> get in is a reasonable solution.
>> 
>> I hereby announce features of Flink 1.9.0 are freezed, *July 11* will
>>> be
>> the
>> day for cutting branch.  Since the feature freeze has effectively took
>> place,
>> I kindly ask committers to refrain from merging features that are
 planned
>> for
>> future releases into the master branch for the time being before the
>>> 1.9
>> branch
>> is cut. We understand this might be a bit inconvenient, thanks for the
>> cooperation here.
>> 
>> Best,
>> Kurt
>> 
>> 
>> On Fri, Jul 5, 2019 at 5:19 PM 罗齐  wrote:
>> 
>>> Hi Gordon,
>>> 
>>> Will branch 1.9 be cut out today? We're really looking forward to the
>>> blink features in 1.9.
>>> 
>>> Thanks,
>>> Qi
>>> 
>>> On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai <
 tzuli...@apache.org>
>>> wrote:
>>> 
 Thanks for the updates so far everyone!
 
 Since support for the new Blink-based Table / SQL runner and
 fine-grained
 recovery are quite prominent features for 1.9.0,
 and developers involved in these topics have already expressed that
 these
 could make good use for another week,
 I think it definitely makes sense to postpone the feature freeze.
 
 The new date for feature freeze and feature branch cut for 1.9.0
>>> will
 be
 *July
 5*.
 
 Please update on this thread if there are any further concerns!
 
 Cheers,
 Gordon
 
 On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler <
>>> ches...@apache.org>
 wrote:
 
> On the fine-grained recovery / batch scheduling side we could make
 good
> use of another week.
> Currently we are on track to have the _feature_ merged, but without
> having done a great deal of end-to-end testing.
> 
> On 25/06/2019 15:01, Kurt Young wrote:
>> Hi Aljoscha,
>> 
>> I also feel an additional week can make the remaining work more
 easy. At
>> least
>> we don't have to check in lots of commits in both branches
>>> (master &
>> release-1.9).
>> 
>> Best,
>> Kurt
>> 
>> 
>> On

[jira] [Created] (FLINK-13235) Change the Netty default transport mode to auto

2019-07-11 Thread zhijiang (JIRA)

zhijiang created FLINK-13235:


 Summary: Change the Netty default transport mode to auto
 Key: FLINK-13235
 URL: https://issues.apache.org/jira/browse/FLINK-13235
 Project: Flink
  Issue Type: Improvement
  Components: Runtime / Network
Reporter: zhijiang
Assignee: zhijiang


The current default config for "taskmanager.net.transport" in 
NettyShuffleEnvironmentOptions is "NIO". In order to use "EPOLL" mode which has 
better performance and is recommended when available, we could change the 
default config as "AUTO". Then the "NIO" mode is used as a fallback.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.9.0 release

Hi qi,

We are about to cut branch, the announce mail will be sent after that.
Sorry for the slight delay.

Best,
Kurt


On Fri, Jul 12, 2019 at 11:43 AM qi luo  wrote:

> Do we have a new timeline for 1.9 branch cut?
>
> Thanks,
> Qi
>
> > On Jul 12, 2019, at 11:42 AM, qi luo  wrote:
> >
> > Any news on this?
> >
> > Thanks,
> > Qi
> >
> >> On Jul 11, 2019, at 11:13 PM, Stephan Ewen  wrote:
> >>
> >> Number (6) is not a feature but a bug fix, so no need to block on
> that...
> >>
> >> On Thu, Jul 11, 2019 at 4:27 PM Kurt Young  wrote:
> >>
> >>> Hi Chesnay,
> >>>
> >>> Here is the JIRA list I have collected, all of them are under
> reviewing:
> >>>
> >>> 1. Hive UDF support (FLINK-13024, FLINK-13225)
> >>> 2. Partition prune support (FLINK-13115)
> >>> 3. Set StreamGraph properties in blink planner (FLINK-13121)
> >>> 4. Support HBase upsert sink (FLINK-10245)
> >>> 5. Support JDBC TableFactory (FLINK-13118)
> >>> 6. Fix the bug of throwing IOException while
> FileBufferReader#nextBuffer
> >>> (FLINK-13110)
> >>> 7. Bookkeeping of available resources of allocated slots in SlotPool
> >>> (FLINK-12765)
> >>> 8. Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
> >>> (FLINK-13187)
> >>> 9. Add support for batch slot requests to SlotPoolImpl (FLINK-13166)
> >>> 10. Complete slot requests in request order (FLINK-13165)
> >>>
> >>> Best,
> >>> Kurt
> >>>
> >>>
> >>> On Thu, Jul 11, 2019 at 6:12 PM Chesnay Schepler 
> >>> wrote:
> >>>
>  Can we get JIRA's attached to these items so people out of the loop
> can
>  track the progress?
> 
>  On 05/07/2019 16:06, Kurt Young wrote:
> > Here are the features I collected which are under actively developing
> >>> and
> > close
> > to merge:
> >
> > 1. Bridge blink planner to unified table environment and remove
>  TableConfig
> > from blink planner
> > 2. Support timestamp with local time zone and partition pruning in
> >>> blink
> > planner
> > 3. Support JDBC & HBase lookup function and upsert sink
> > 4. StreamExecutionEnvironment supports executing job with
> StreamGraph,
>  and
> > blink planner should set proper properties to StreamGraph
> > 5. Set resource profiles to task and enable managed memory as
> resource
> > profile
> >
> > Best,
> > Kurt
> >
> >
> > On Fri, Jul 5, 2019 at 9:37 PM Kurt Young  wrote:
> >
> >> Hi devs,
> >>
> >> It's July 5 now and we should announce feature freeze and cut the
> >>> branch
> >> as planned. However, some components seems still not ready yet and
> >> various features are still under development or review.
> >>
> >> But we also can not extend the freeze day again which will further
> >>> delay
> >> the
> >> release date. I think freeze new features today and have another
> >>> couple
> >> of buffer days, letting features which are almost ready have a
> chance
> >>> to
> >> get in is a reasonable solution.
> >>
> >> I hereby announce features of Flink 1.9.0 are freezed, *July 11*
> will
> >>> be
> >> the
> >> day for cutting branch.  Since the feature freeze has effectively
> took
> >> place,
> >> I kindly ask committers to refrain from merging features that are
>  planned
> >> for
> >> future releases into the master branch for the time being before the
> >>> 1.9
> >> branch
> >> is cut. We understand this might be a bit inconvenient, thanks for
> the
> >> cooperation here.
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Fri, Jul 5, 2019 at 5:19 PM 罗齐  wrote:
> >>
> >>> Hi Gordon,
> >>>
> >>> Will branch 1.9 be cut out today? We're really looking forward to
> the
> >>> blink features in 1.9.
> >>>
> >>> Thanks,
> >>> Qi
> >>>
> >>> On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai <
>  tzuli...@apache.org>
> >>> wrote:
> >>>
>  Thanks for the updates so far everyone!
> 
>  Since support for the new Blink-based Table / SQL runner and
>  fine-grained
>  recovery are quite prominent features for 1.9.0,
>  and developers involved in these topics have already expressed
> that
>  these
>  could make good use for another week,
>  I think it definitely makes sense to postpone the feature freeze.
> 
>  The new date for feature freeze and feature branch cut for 1.9.0
> >>> will
>  be
>  *July
>  5*.
> 
>  Please update on this thread if there are any further concerns!
> 
>  Cheers,
>  Gordon
> 
>  On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler <
> >>> ches...@apache.org>
>  wrote:
> 
> > On the fine-grained recovery / batch scheduling side we could
> make
>  good
> > use of another week.
> > Currently we are on track to have the _feature_ merged, but
> withou

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Jeff Zhang

Congrats, Rong!


vino yang  于2019年7月12日周五 上午10:08写道：

> congratulations Rong Rong!
>
> Fabian Hueske  于2019年7月11日周四 下午10:25写道：
>
>> Hi everyone,
>>
>> I'm very happy to announce that Rong Rong accepted the offer of the Flink
>> PMC to become a committer of the Flink project.
>>
>> Rong has been contributing to Flink for many years, mainly working on SQL
>> and Yarn security features. He's also frequently helping out on the
>> user@f.a.o mailing lists.
>>
>> Congratulations Rong!
>>
>> Best, Fabian
>> (on behalf of the Flink PMC)
>>
>

-- 
Best Regards

Jeff Zhang

[jira] [Created] (FLINK-13236) Fix bug and improve performance in TopNBuffer

2019-07-11 Thread Caizhi Weng (JIRA)

Caizhi Weng created FLINK-13236:
---

 Summary: Fix bug and improve performance in TopNBuffer
 Key: FLINK-13236
 URL: https://issues.apache.org/jira/browse/FLINK-13236
 Project: Flink
  Issue Type: Improvement
Reporter: Caizhi Weng
Assignee: Caizhi Weng


In {{TopNBuffer}} we have the following method:

{code:java}
/**
 * Puts a record list into the buffer under the sortKey.
 * Note: if buffer already contains sortKey, putAll will overwrite the previous 
value
 *
 * @param sortKey sort key with which the specified values are to be associated
 * @param values record lists to be associated with the specified key
 */
void putAll(BaseRow sortKey, Collection values) {
treeMap.put(sortKey, values);
currentTopNum += values.size();
}
{code}

When {{sortKey}} already exists in {{treeMap}}, the {{currentTopNum}} should be 
first subtracted by the old {{value.size()}} in {{treeMap}} then added (can't 
be directly added). As currently only {{AppendOnlyTopNFunction}} uses this 
method in its init procedure, this bug is not triggered.


{code:java}
/**
 * Gets record which rank is given value.
 *
 * @param rank rank value to search
 * @return the record which rank is given value
 */
BaseRow getElement(int rank) {
int curRank = 0;
Iterator>> iter = 
treeMap.entrySet().iterator();
while (iter.hasNext()) {
Map.Entry> entry = iter.next();
Collection list = entry.getValue();

Iterator listIter = list.iterator();
while (listIter.hasNext()) {
BaseRow elem = listIter.next();
curRank += 1;
if (curRank == rank) {
return elem;
}
}
}
return null;
}
{code}

We can remove the inner loop by adding {{curRank}} by {{list.size()}} each time.




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.9.0 release

2019-07-11 Thread qi luo

No worries. Glad to know the progress :-)

> On Jul 12, 2019, at 11:53 AM, Kurt Young  wrote:
> 
> Hi qi,
> 
> We are about to cut branch, the announce mail will be sent after that.
> Sorry for the slight delay.
> 
> Best,
> Kurt
> 
> 
> On Fri, Jul 12, 2019 at 11:43 AM qi luo  wrote:
> 
>> Do we have a new timeline for 1.9 branch cut?
>> 
>> Thanks,
>> Qi
>> 
>>> On Jul 12, 2019, at 11:42 AM, qi luo  wrote:
>>> 
>>> Any news on this?
>>> 
>>> Thanks,
>>> Qi
>>> 
 On Jul 11, 2019, at 11:13 PM, Stephan Ewen  wrote:
 
 Number (6) is not a feature but a bug fix, so no need to block on
>> that...
 
 On Thu, Jul 11, 2019 at 4:27 PM Kurt Young  wrote:
 
> Hi Chesnay,
> 
> Here is the JIRA list I have collected, all of them are under
>> reviewing:
> 
> 1. Hive UDF support (FLINK-13024, FLINK-13225)
> 2. Partition prune support (FLINK-13115)
> 3. Set StreamGraph properties in blink planner (FLINK-13121)
> 4. Support HBase upsert sink (FLINK-10245)
> 5. Support JDBC TableFactory (FLINK-13118)
> 6. Fix the bug of throwing IOException while
>> FileBufferReader#nextBuffer
> (FLINK-13110)
> 7. Bookkeeping of available resources of allocated slots in SlotPool
> (FLINK-12765)
> 8. Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
> (FLINK-13187)
> 9. Add support for batch slot requests to SlotPoolImpl (FLINK-13166)
> 10. Complete slot requests in request order (FLINK-13165)
> 
> Best,
> Kurt
> 
> 
> On Thu, Jul 11, 2019 at 6:12 PM Chesnay Schepler 
> wrote:
> 
>> Can we get JIRA's attached to these items so people out of the loop
>> can
>> track the progress?
>> 
>> On 05/07/2019 16:06, Kurt Young wrote:
>>> Here are the features I collected which are under actively developing
> and
>>> close
>>> to merge:
>>> 
>>> 1. Bridge blink planner to unified table environment and remove
>> TableConfig
>>> from blink planner
>>> 2. Support timestamp with local time zone and partition pruning in
> blink
>>> planner
>>> 3. Support JDBC & HBase lookup function and upsert sink
>>> 4. StreamExecutionEnvironment supports executing job with
>> StreamGraph,
>> and
>>> blink planner should set proper properties to StreamGraph
>>> 5. Set resource profiles to task and enable managed memory as
>> resource
>>> profile
>>> 
>>> Best,
>>> Kurt
>>> 
>>> 
>>> On Fri, Jul 5, 2019 at 9:37 PM Kurt Young  wrote:
>>> 
 Hi devs,
 
 It's July 5 now and we should announce feature freeze and cut the
> branch
 as planned. However, some components seems still not ready yet and
 various features are still under development or review.
 
 But we also can not extend the freeze day again which will further
> delay
 the
 release date. I think freeze new features today and have another
> couple
 of buffer days, letting features which are almost ready have a
>> chance
> to
 get in is a reasonable solution.
 
 I hereby announce features of Flink 1.9.0 are freezed, *July 11*
>> will
> be
 the
 day for cutting branch.  Since the feature freeze has effectively
>> took
 place,
 I kindly ask committers to refrain from merging features that are
>> planned
 for
 future releases into the master branch for the time being before the
> 1.9
 branch
 is cut. We understand this might be a bit inconvenient, thanks for
>> the
 cooperation here.
 
 Best,
 Kurt
 
 
 On Fri, Jul 5, 2019 at 5:19 PM 罗齐  wrote:
 
> Hi Gordon,
> 
> Will branch 1.9 be cut out today? We're really looking forward to
>> the
> blink features in 1.9.
> 
> Thanks,
> Qi
> 
> On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai <
>> tzuli...@apache.org>
> wrote:
> 
>> Thanks for the updates so far everyone!
>> 
>> Since support for the new Blink-based Table / SQL runner and
>> fine-grained
>> recovery are quite prominent features for 1.9.0,
>> and developers involved in these topics have already expressed
>> that
>> these
>> could make good use for another week,
>> I think it definitely makes sense to postpone the feature freeze.
>> 
>> The new date for feature freeze and feature branch cut for 1.9.0
> will
>> be
>> *July
>> 5*.
>> 
>> Please update on this thread if there are any further concerns!
>> 
>> Cheers,
>> Gordon
>> 
>> On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler <
> ches...@apache.org>
>> wrote:
>> 
>>> On the fine-grained r

Confused by the `projectFields` Method in `ProjectableTableSource` Interface

2019-07-11 Thread Caizhi Weng

Hi Flink developers,

When implementing `JDBCTableSource` with `ProjectableTableSource` interface
I'm confused by the `projectFields` method.

The java doc of the `projectFields` states that (It also has a typo...
poduced -> produced):

> Creates a copy of the {@link TableSource} that projects its output to the
> given field indexes.
> The field indexes relate to the physical poduced data type ({@link
> TableSource#getProducedDataType()}) and not to the table schema ({@link
> TableSource#getTableSchema} of the {@link TableSource}.


So my understanding of this java doc is that, if the table schema of the
source is {a: Int, b: Double, c: String, d: Long} and the produced data
type of the source is {a: Int, c: String, d: Long}. Then if user writes "select
c, d from my_table" then the project field indices should be {1, 2} instead
of {2, 3} (because they should be related to the produced type and not to
the schema).

But the implementation of `CSVTableSource` says otherwise. The field
indices are related to the schema, not to the produced data type.

I pick the implementation of `CSVTableSource` to implement JDBC table
source (as `CSVTableSource` obviously passed all the test cases). So which
one is correct, my understanding on the java doc or the implementation of
`CSVTableSource`?

Thanks.

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

2019-07-11 Thread Hequn Cheng

Congratulations Rong!

Best, Hequn

On Fri, Jul 12, 2019 at 12:19 PM Jeff Zhang  wrote:

> Congrats, Rong!
>
>
> vino yang  于2019年7月12日周五 上午10:08写道：
>
>> congratulations Rong Rong!
>>
>> Fabian Hueske  于2019年7月11日周四 下午10:25写道：
>>
>>> Hi everyone,
>>>
>>> I'm very happy to announce that Rong Rong accepted the offer of the
>>> Flink PMC to become a committer of the Flink project.
>>>
>>> Rong has been contributing to Flink for many years, mainly working on
>>> SQL and Yarn security features. He's also frequently helping out on the
>>> user@f.a.o mailing lists.
>>>
>>> Congratulations Rong!
>>>
>>> Best, Fabian
>>> (on behalf of the Flink PMC)
>>>
>>
>
> --
> Best Regards
>
> Jeff Zhang
>

request contributor permission

2019-07-11 Thread ????

Hi,

I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is kangzai

Apply for being a contributor

2019-07-11 Thread 胡伟华

Hi, 

I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is huwh, my fullname is HuWeihua.

Thanks a lot.

[jira] [Created] (FLINK-13237) Add expression table api test to blink

Jingsong Lee created FLINK-13237:


 Summary: Add expression table api test to blink
 Key: FLINK-13237
 URL: https://issues.apache.org/jira/browse/FLINK-13237
 Project: Flink
  Issue Type: New Feature
  Components: Table SQL / Planner
Reporter: Jingsong Lee
Assignee: Jingsong Lee






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13238) Reduce blink planner's testing time

Kurt Young created FLINK-13238:
--

 Summary: Reduce blink planner's testing time
 Key: FLINK-13238
 URL: https://issues.apache.org/jira/browse/FLINK-13238
 Project: Flink
  Issue Type: Improvement
  Components: Table SQL / Planner
Reporter: Kurt Young


The blink planner has an independent CI profile, but still exceeded 50 min 
limit from time to time. We need to optimize the tests to reduce the testing 
time. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (FLINK-13239) Add unary loss functions

2019-07-11 Thread Xu Yang (JIRA)

Xu Yang created FLINK-13239:
---

 Summary: Add unary loss functions
 Key: FLINK-13239
 URL: https://issues.apache.org/jira/browse/FLINK-13239
 Project: Flink
  Issue Type: Sub-task
  Components: Library / Machine Learning
Reporter: Xu Yang
Assignee: Xu Yang


Add unary loss function's interface and 9 common used functions:
# ExponentialLossFunc
# HingeLossFunc
# LogisticLossFunc
# LogLossFunc
# PerceptronLossFunc
# ZeroOneLossFunc
# SquareLossFunc
# SvrLossFunc
# HuberLossFunc

More information about loss function, please see：
* https://en.wikipedia.org/wiki/Loss_function
* https://en.wikipedia.org/wiki/Loss_functions_for_classification



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[ANNOUNCE] Flink 1.9 release branch has been created