[jira] [Created] (FLINK-7179) Projectable ProjectableTableSource interface doesn't compatible with BoundedOutOfOrdernessTimestampExtractor

[Zhenqiu Huang (JIRA)]

Zhenqiu Huang created FLINK-7179:


 Summary: Projectable ProjectableTableSource interface doesn't 
compatible with BoundedOutOfOrdernessTimestampExtractor
 Key: FLINK-7179
 URL: https://issues.apache.org/jira/browse/FLINK-7179
 Project: Flink
  Issue Type: Bug
  Components: Table API & SQL
Affects Versions: 1.3.1
Reporter: Zhenqiu Huang


In the implementation of window of stream sql, 
BoundedOutOfOrdernessTimestampExtractor is designed to extract row time from 
each row. It assumes the ts field is in the data stream by default. On the 
other hand, ProjectableTableSource is designed to help projection push down. If 
there is no row time related field in a query, the extractor can't function 
well. 









--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (FLINK-7178) Datadog Metric Reporter Jar is Lacking Dependencies

[Elias Levy (JIRA)]

Elias Levy created FLINK-7178:
-

 Summary: Datadog Metric Reporter Jar is Lacking Dependencies
 Key: FLINK-7178
 URL: https://issues.apache.org/jira/browse/FLINK-7178
 Project: Flink
  Issue Type: Bug
  Components: Metrics
Affects Versions: 1.3.1
Reporter: Elias Levy


The Datadog metric reporter has dependencies on {{com.squareup.okhttp3}} and 
{{com.squareup.okio}}.  It appears there was an attempt to Maven Shade plug-in 
to move these classes to {{org.apache.flink.shaded.okhttp3}} and 
{{org.apache.flink.shaded.okio}} during packaging.  Alas, the shaded classes 
are not included in the {{flink-metrics-datadog-1.3.1.jar}} released to Maven 
Central.  Using the Jar results in an error when the Jobmanager or Taskmanager 
starts up because of the missing dependencies. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (FLINK-7177) [table] Using Table API to perform aggregation on another Table API / SQL result table causes runVolcanoPlanner failed on physicalPlan generation

[Rong Rong (JIRA)]

Rong Rong created FLINK-7177:


 Summary: [table] Using Table API to perform aggregation on another 
Table API / SQL result table causes runVolcanoPlanner failed on physicalPlan 
generation
 Key: FLINK-7177
 URL: https://issues.apache.org/jira/browse/FLINK-7177
 Project: Flink
  Issue Type: Bug
Reporter: Rong Rong


For example:
```
val env = ExecutionEnvironment.getExecutionEnvironment
val tEnv = TableEnvironment.getTableEnvironment(env, config)
val inputTable = 
CollectionDataSets.getSmallNestedTupleDataSet(env).toTable(tEnv, 'a, 'b)
val resultTable = inputTable.select('a, 'b).where('a.get("_1") > 0)
val failingTable = resultTable.select('a.get("_1").avg, 'a.get("_2").sum, 
'b.count)
```

Details can be found in: 
https://github.com/apache/flink/compare/master...walterddr:bug_report_sql_query_result_consume_by_table_api



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (FLINK-7176) Failed builds (due to compilation) don't upload logs

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-7176:
---

 Summary: Failed builds (due to compilation) don't upload logs
 Key: FLINK-7176
 URL: https://issues.apache.org/jira/browse/FLINK-7176
 Project: Flink
  Issue Type: Bug
  Components: Travis
Affects Versions: 1.4.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.4.0


If the compile phase fails on travis {{flink-dist}} may not be created. This 
causes the check for the inclusion of snappy in {{flink-dist}} to fail.

The function doing this check calls {{exit 1}} on error, which exits the entire 
shell, thus skipping subsequent actions like the upload of logs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (FLINK-7175) Add simple benchmark suite for Flink

[Piotr Nowojski (JIRA)]

Piotr Nowojski created FLINK-7175:
-

 Summary: Add simple benchmark suite for Flink
 Key: FLINK-7175
 URL: https://issues.apache.org/jira/browse/FLINK-7175
 Project: Flink
  Issue Type: Improvement
Reporter: Piotr Nowojski
Assignee: Piotr Nowojski


For a long term goal it would be great to have both full scale (with real 
clusters) and micro benchmarks suites that runs automatically against each PR 
and constantly against master branch.

First step towards this is to implement some local micro benchmarks, that run 
some simple Flink applications on local Flink cluster. Developers could use 
those benchmarks manually to test their changes.

After that, we could setup some simple automation tool that would run those 
benchmarks against master branch on some old computer/laptop. We could publish 
it to our instance of [Codespeed|https://github.com/tobami/codespeed] project 
(example instance for pypy project: [PyPy Speed Center|http://speed.pypy.org/])



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Request for contributor permissions

[Aljoscha Krettek]

Hi,

I added you to the list of contributors. Welcome to the community! :-)

Best,
Aljoscha

> On 13. Jul 2017, at 16:16, 周思华  wrote:
> 
> Hi devs,
> I'm very interested in Flink and willing to contribute to it. Cloud anybody 
> give me the contributor permissions? My jira username is "sihuazhou".
> Thanks~
> Regards,
> Sihua Zhou

Ship files to flink on yarn-cluster mode

[Guy Harmach]

Hi,

Is there a way to ship files to a flink job running on YARN (similar to -files 
flag in Spark)?
According the flink cli usage there is a  -yarnship flag, but no documentation 
how to use it and retrieve the files on the flink job.
If it is possible, I'd appreciate a reference to an example of sending a file 
and reading it.

Thanks, Guy
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

Re: [POLL] Who still uses Java 7 with Flink ?

[Seth Wiesman]

+1 for dropping java 7 

On 7/13/17, 4:59 AM, "Konstantin Knauf"  wrote:

+1 for dropping Java 7

On 13.07.2017 10:11, Niels Basjes wrote:
> +1 For dropping java 1.7
> 
> On 13 Jul 2017 04:11, "Jark Wu"  wrote:
> 
>> +1 for dropping Java 7
>>
>> 2017-07-13 9:34 GMT+08:00 ☼ R Nair (रविशंकर नायर) <
>> ravishankar.n...@gmail.com>:
>>
>>> +1 for dropping Java 1.7.
>>>
>>> On Wed, Jul 12, 2017 at 9:10 PM, Kurt Young  wrote:
>>>
 +1 for droppint Java 7, we have been using Java 8 for more than one 
year
 in Alibaba and everything work fine.

 Best,
 Kurt

 On Thu, Jul 13, 2017 at 2:53 AM, Bowen Li 
 wrote:

> +1 for dropping Java 7
>
> On Wed, Jul 12, 2017 at 9:04 AM, Gyula Fóra 
> wrote:
>
>> +1 for dropping 1.7 from me as well.
>>
>> Gyula
>>
>> On Wed, Jul 12, 2017, 17:53 Ted Yu  wrote:
>>
>>> +1 on dropping support for Java 1.7
>>>
>>>  Original message 
>>> From: Robert Metzger 
>>> Date: 7/12/17 8:36 AM (GMT-08:00)
>>> To: dev@flink.apache.org
>>> Cc: user 
>>> Subject: Re: [POLL] Who still uses Java 7 with Flink ?
>>>
>>> +1 to drop Java 7 support
>>>
>>> I believe that we can move to Java 8 for the argument you've stated.
>>> ElasticSearch 5, Spark 2.2  require Java 8 already, Hadoop 3.0.0
> will
>>> require it as well.
>>>
>>> On Wed, Jul 12, 2017 at 4:02 PM, Driesprong, Fokko
> >>
>>> wrote:
>>>
 Hi,

 I would be in favor of dropping Java 7 as we don't use it in our
> hadoop
 infra (and we are a bank). Also, Spark 2.2 has been released today,
 which doesn't
 support Java 7  ses/spark-release-2-2-0.
>> html
>
 anymore, and Flink should not lack behind :-)

 Cheers, Fokko

 2017-07-12 15:56 GMT+02:00 Stephan Ewen :

> Bumping this thread again.
>
> There are several strong points for dropping Java 7 support,
> apart
>> from
 the
> fact that it is not maintained
>
>   - We could really use the Java 8 default methods feature in
 interfaces to
> evolve the API without breaking backwards compatibility
>
>   - Easier build setup for Scala 2.12 (which requires Java 8),
> no need
 to
> manage the tricky combinations of Java / Scala versions
>
>   - Ability to use vanilla Akka (rather than Flakka) which
> requires
 Java 8.
> - Fewer problems for users that use Akka in the Flink
> applications
> - Flakka currently does not support Scala 2.12
> - Newer Akka versions shade protobuf, which is important
>
> I think these together make a pretty good case for bumping the
>> required
> Java version to Java 8.
>
> It would just help both Flink users (dependency management, Scala
 versions)
> and developers (build simplification) a lot.
> Unless we see users stepping forward and making a case that it
> will be
> impossible for them to upgrade to Java 8, I suggest to go
> forward with
> this.
>
> Best,
> Stephan
>
>
>
> On Thu, Jun 8, 2017 at 9:36 PM, Haohui Mai 
>> wrote:
>
>> +1
>>
>> There are several high impacts security vulnerabilities in JDK
> 7 and
 will
>> not be addressed.
>>
>> As a result we completely moved away from JDK 7.
>>
>> +1 on separating the tasks of supporting Scala 2.12 and JDK 8
> in two
> steps.
>>
>>
>> On Thu, Jun 8, 2017 at 9:53 AM Greg Hogan 
>> wrote:
>>
>>> Is this not two different issues?
>>> - adding builds for Scala 2.12
>>> - upgrading to Java version 1.8
>>>
>>> It may be time to switch, but I haven’t seen anything in
>> FLINK-5005
> which
 

[jira] [Created] (FLINK-7174) Bump dependency of Kafka 0.10.x to the latest one

[Piotr Nowojski (JIRA)]

Piotr Nowojski created FLINK-7174:
-

 Summary: Bump dependency of Kafka 0.10.x to the latest one
 Key: FLINK-7174
 URL: https://issues.apache.org/jira/browse/FLINK-7174
 Project: Flink
  Issue Type: Improvement
Reporter: Piotr Nowojski
Assignee: Piotr Nowojski


We are using pretty old Kafka version for 0.10. Besides any bug fixes and 
improvements that were made between 0.10.0.1 and 0.10.2.1, it 0.10.2.1 version 
is more similar to 0.11.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Feel confused for the illustration of tumbling window

[Aljoscha Krettek]

Ah I see, then we should fix that.

> On 13. Jul 2017, at 12:45, jincheng sun  wrote:
> 
> Thanks Fabian, that's my meaning. -:)
> 
> 2017-07-13 18:14 GMT+08:00 Fabian Hueske :
> 
>> I think the point is that some elements are drawn on the window boundary.
>> So it is not clear to which window they would belong.
>> 
>> 2017-07-13 12:03 GMT+02:00 Aljoscha Krettek :
>> 
>>> Hi,
>>> 
>>> How do you mean? The windows in the illustration are not overlapping.
>>> 
>>> I’m very happy about suggestions for improving this, though, if anyone
>> has
>>> one. 
>>> 
>>> Best,
>>> Aljoscha
 On 13. Jul 2017, at 11:43, jincheng sun 
>>> wrote:
 
 Hi guys,
Feel confused for the illustration of tumbling window, as follows:
 
 
 ​https://ci.apache.org/projects/flink/flink-docs-
>>> release-1.3/dev/windows.html#tumbling-windows
>>> https://ci.apache.org/projects/flink/
>>> flink-docs-release-1.3/dev/windows.html#tumbling-windows>
 https://ci.apache.org/projects/flink/flink-docs-
>>> release-1.3/fig/tumbling-windows.svg >> projects/flink/flink-docs-release-1.3/fig/tumbling-windows.svg>
 
 The Tumbling windows have a fiexd size and do not overlap, i,e.,
>>> every element should be in one window.
 So, The illustration above may be confused flink user.
 
  What do you think? Welcome anybody to feedback.
 
 Thanks,
 Jincheng
 
>>> 
>>> 
>> 

Re: Feel confused for the illustration of tumbling window

[jincheng sun]

Thanks Fabian, that's my meaning. -:)

2017-07-13 18:14 GMT+08:00 Fabian Hueske :

> I think the point is that some elements are drawn on the window boundary.
> So it is not clear to which window they would belong.
>
> 2017-07-13 12:03 GMT+02:00 Aljoscha Krettek :
>
> > Hi,
> >
> > How do you mean? The windows in the illustration are not overlapping.
> >
> > I’m very happy about suggestions for improving this, though, if anyone
> has
> > one. 
> >
> > Best,
> > Aljoscha
> > > On 13. Jul 2017, at 11:43, jincheng sun 
> > wrote:
> > >
> > > Hi guys,
> > > Feel confused for the illustration of tumbling window, as follows:
> > >
> > >
> > > ​https://ci.apache.org/projects/flink/flink-docs-
> > release-1.3/dev/windows.html#tumbling-windows
> > https://ci.apache.org/projects/flink/
> > flink-docs-release-1.3/dev/windows.html#tumbling-windows>
> > > https://ci.apache.org/projects/flink/flink-docs-
> > release-1.3/fig/tumbling-windows.svg  > projects/flink/flink-docs-release-1.3/fig/tumbling-windows.svg>
> > >
> > >  The Tumbling windows have a fiexd size and do not overlap, i,e.,
> > every element should be in one window.
> > > So, The illustration above may be confused flink user.
> > >
> > >   What do you think? Welcome anybody to feedback.
> > >
> > > Thanks,
> > > Jincheng
> > >
> >
> >
>

[jira] [Created] (FLINK-7172) Add a event logical id field to ValueTimeWrapper

[Yueting Chen (JIRA)]

Yueting Chen created FLINK-7172:
---

 Summary: Add a event logical id field to ValueTimeWrapper
 Key: FLINK-7172
 URL: https://issues.apache.org/jira/browse/FLINK-7172
 Project: Flink
  Issue Type: Improvement
Reporter: Yueting Chen


In order to address FLINK-7169, we need to know the logical order of the input 
events. This issue aims to add a logical id field to ValueTimeWrapper. This 
requires some modifications from `AbstractKeyedCEPPatternOperator` to 
`ValueTimeWrapper` 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Feel confused for the illustration of tumbling window

[Fabian Hueske]

I think the point is that some elements are drawn on the window boundary.
So it is not clear to which window they would belong.

2017-07-13 12:03 GMT+02:00 Aljoscha Krettek :

> Hi,
>
> How do you mean? The windows in the illustration are not overlapping.
>
> I’m very happy about suggestions for improving this, though, if anyone has
> one. 
>
> Best,
> Aljoscha
> > On 13. Jul 2017, at 11:43, jincheng sun 
> wrote:
> >
> > Hi guys,
> > Feel confused for the illustration of tumbling window, as follows:
> >
> >
> > ​https://ci.apache.org/projects/flink/flink-docs-
> release-1.3/dev/windows.html#tumbling-windows
> https://ci.apache.org/projects/flink/
> flink-docs-release-1.3/dev/windows.html#tumbling-windows>
> > https://ci.apache.org/projects/flink/flink-docs-
> release-1.3/fig/tumbling-windows.svg  projects/flink/flink-docs-release-1.3/fig/tumbling-windows.svg>
> >
> >  The Tumbling windows have a fiexd size and do not overlap, i,e.,
> every element should be in one window.
> > So, The illustration above may be confused flink user.
> >
> >   What do you think? Welcome anybody to feedback.
> >
> > Thanks,
> > Jincheng
> >
>
>

[jira] [Created] (FLINK-7171) Remove identity project for time attributes

[Timo Walther (JIRA)]

Timo Walther created FLINK-7171:
---

 Summary: Remove identity project for time attributes
 Key: FLINK-7171
 URL: https://issues.apache.org/jira/browse/FLINK-7171
 Project: Flink
  Issue Type: Improvement
  Components: Table API & SQL
Reporter: Timo Walther


If only time attributes are projected away, the translated plan should not 
contain an additional Calc node.

Example:
{code}
streamUtil.addTable[(Int, String, Long)](
"MyTable", 'a, 'b, 'c, 'proctime.proctime, 'rowtime.rowtime)
{code}

and 

{code}
streamUtil.addTable[(Int, String, Long)](
"MyTable", 'a, 'b, 'c)
{code}

Lead to different logical plans even if these attributes are not accessed in 
{{"SELECT DISTINCT a, b, c FROM MyTable"}}.

{code}
  unaryNode(
"DataStreamGroupAggregate",
unaryNode(
  "DataStreamCalc",
  streamTableNode(0),
  term("select", "a, b, c")
),
term("groupBy", "a, b, c"),
term("select", "a, b, c")
  )
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Feel confused for the illustration of tumbling window

[Aljoscha Krettek]

Hi,

How do you mean? The windows in the illustration are not overlapping.

I’m very happy about suggestions for improving this, though, if anyone has one. 


Best,
Aljoscha
> On 13. Jul 2017, at 11:43, jincheng sun  wrote:
> 
> Hi guys,
> Feel confused for the illustration of tumbling window, as follows:
> 
> 
> ​https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/windows.html#tumbling-windows
>  
> https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/windows.html#tumbling-windows>
> https://ci.apache.org/projects/flink/flink-docs-release-1.3/fig/tumbling-windows.svg
>  
> 
> 
>  The Tumbling windows have a fiexd size and do not overlap, i,e., every 
> element should be in one window. 
> So, The illustration above may be confused flink user. 
> 
>   What do you think? Welcome anybody to feedback.
> 
> Thanks, 
> Jincheng
> 

Feel confused for the illustration of tumbling window

[jincheng sun]

Hi guys,
Feel confused for the illustration of tumbling window, as follows:


​https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/windows.html#tumbling-windows
https://ci.apache.org/projects/flink/flink-docs-release-1.3/fig/tumbling-windows.svg

 The Tumbling windows have a fiexd size and do not overlap, i,e., every
element should be in one window.
So, The illustration above may be confused flink user.

  What do you think? Welcome anybody to feedback.

Thanks,
Jincheng

Re: [POLL] Who still uses Java 7 with Flink ?

[Stephan Ewen]

Thanks a lot for the feedback. Let's keep this thread open for feedback
till end of the week.

If it stays like it is (all or a vast majority in favor of dropping Java 7
support), we should start dropping Java 7 from next week on.


On Thu, Jul 13, 2017 at 10:59 AM, Konstantin Knauf <
konstantin.kn...@tngtech.com> wrote:

> +1 for dropping Java 7
>
> On 13.07.2017 10:11, Niels Basjes wrote:
> > +1 For dropping java 1.7
> >
> > On 13 Jul 2017 04:11, "Jark Wu"  wrote:
> >
> >> +1 for dropping Java 7
> >>
> >> 2017-07-13 9:34 GMT+08:00 ☼ R Nair (रविशंकर नायर) <
> >> ravishankar.n...@gmail.com>:
> >>
> >>> +1 for dropping Java 1.7.
> >>>
> >>> On Wed, Jul 12, 2017 at 9:10 PM, Kurt Young  wrote:
> >>>
>  +1 for droppint Java 7, we have been using Java 8 for more than one
> year
>  in Alibaba and everything work fine.
> 
>  Best,
>  Kurt
> 
>  On Thu, Jul 13, 2017 at 2:53 AM, Bowen Li 
>  wrote:
> 
> > +1 for dropping Java 7
> >
> > On Wed, Jul 12, 2017 at 9:04 AM, Gyula Fóra 
> > wrote:
> >
> >> +1 for dropping 1.7 from me as well.
> >>
> >> Gyula
> >>
> >> On Wed, Jul 12, 2017, 17:53 Ted Yu  wrote:
> >>
> >>> +1 on dropping support for Java 1.7
> >>>
> >>>  Original message 
> >>> From: Robert Metzger 
> >>> Date: 7/12/17 8:36 AM (GMT-08:00)
> >>> To: dev@flink.apache.org
> >>> Cc: user 
> >>> Subject: Re: [POLL] Who still uses Java 7 with Flink ?
> >>>
> >>> +1 to drop Java 7 support
> >>>
> >>> I believe that we can move to Java 8 for the argument you've
> stated.
> >>> ElasticSearch 5, Spark 2.2  require Java 8 already, Hadoop 3.0.0
> > will
> >>> require it as well.
> >>>
> >>> On Wed, Jul 12, 2017 at 4:02 PM, Driesprong, Fokko
> >  >>>
> >>> wrote:
> >>>
>  Hi,
> 
>  I would be in favor of dropping Java 7 as we don't use it in our
> > hadoop
>  infra (and we are a bank). Also, Spark 2.2 has been released
> today,
>  which doesn't
>  support Java 7  > ses/spark-release-2-2-0.
> >> html
> >
>  anymore, and Flink should not lack behind :-)
> 
>  Cheers, Fokko
> 
>  2017-07-12 15:56 GMT+02:00 Stephan Ewen :
> 
> > Bumping this thread again.
> >
> > There are several strong points for dropping Java 7 support,
> > apart
> >> from
>  the
> > fact that it is not maintained
> >
> >   - We could really use the Java 8 default methods feature in
>  interfaces to
> > evolve the API without breaking backwards compatibility
> >
> >   - Easier build setup for Scala 2.12 (which requires Java 8),
> > no need
>  to
> > manage the tricky combinations of Java / Scala versions
> >
> >   - Ability to use vanilla Akka (rather than Flakka) which
> > requires
>  Java 8.
> > - Fewer problems for users that use Akka in the Flink
> > applications
> > - Flakka currently does not support Scala 2.12
> > - Newer Akka versions shade protobuf, which is important
> >
> > I think these together make a pretty good case for bumping the
> >> required
> > Java version to Java 8.
> >
> > It would just help both Flink users (dependency management, Scala
>  versions)
> > and developers (build simplification) a lot.
> > Unless we see users stepping forward and making a case that it
> > will be
> > impossible for them to upgrade to Java 8, I suggest to go
> > forward with
> > this.
> >
> > Best,
> > Stephan
> >
> >
> >
> > On Thu, Jun 8, 2017 at 9:36 PM, Haohui Mai 
> >> wrote:
> >
> >> +1
> >>
> >> There are several high impacts security vulnerabilities in JDK
> > 7 and
>  will
> >> not be addressed.
> >>
> >> As a result we completely moved away from JDK 7.
> >>
> >> +1 on separating the tasks of supporting Scala 2.12 and JDK 8
> > in two
> > steps.
> >>
> >>
> >> On Thu, Jun 8, 2017 at 9:53 AM Greg Hogan 
> >> wrote:
> >>
> >>> Is this not two different issues?
> >>> - adding builds for Scala 2.12
> >>> - upgrading to Java version 1.8
> >>>
> >>> It may be time to switch, but I haven’t seen anything in
> >> FLINK-5005
> > which
> >>> prevents simply adding Scala 2.12 to our supported 

[jira] [Created] (FLINK-7170) Fix until condition when the contiguity is strict

[Dian Fu (JIRA)]

Dian Fu created FLINK-7170:
--

 Summary: Fix until condition when the contiguity is strict
 Key: FLINK-7170
 URL: https://issues.apache.org/jira/browse/FLINK-7170
 Project: Flink
  Issue Type: Bug
Reporter: Dian Fu
Assignee: Dian Fu


When the contiguity is {{STRICT}}, the method {{extendWithUntilCondition}} is 
not correct.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [POLL] Who still uses Java 7 with Flink ?

[Konstantin Knauf]

+1 for dropping Java 7

On 13.07.2017 10:11, Niels Basjes wrote:
> +1 For dropping java 1.7
> 
> On 13 Jul 2017 04:11, "Jark Wu"  wrote:
> 
>> +1 for dropping Java 7
>>
>> 2017-07-13 9:34 GMT+08:00 ☼ R Nair (रविशंकर नायर) <
>> ravishankar.n...@gmail.com>:
>>
>>> +1 for dropping Java 1.7.
>>>
>>> On Wed, Jul 12, 2017 at 9:10 PM, Kurt Young  wrote:
>>>
 +1 for droppint Java 7, we have been using Java 8 for more than one year
 in Alibaba and everything work fine.

 Best,
 Kurt

 On Thu, Jul 13, 2017 at 2:53 AM, Bowen Li 
 wrote:

> +1 for dropping Java 7
>
> On Wed, Jul 12, 2017 at 9:04 AM, Gyula Fóra 
> wrote:
>
>> +1 for dropping 1.7 from me as well.
>>
>> Gyula
>>
>> On Wed, Jul 12, 2017, 17:53 Ted Yu  wrote:
>>
>>> +1 on dropping support for Java 1.7
>>>
>>>  Original message 
>>> From: Robert Metzger 
>>> Date: 7/12/17 8:36 AM (GMT-08:00)
>>> To: dev@flink.apache.org
>>> Cc: user 
>>> Subject: Re: [POLL] Who still uses Java 7 with Flink ?
>>>
>>> +1 to drop Java 7 support
>>>
>>> I believe that we can move to Java 8 for the argument you've stated.
>>> ElasticSearch 5, Spark 2.2  require Java 8 already, Hadoop 3.0.0
> will
>>> require it as well.
>>>
>>> On Wed, Jul 12, 2017 at 4:02 PM, Driesprong, Fokko
> >>
>>> wrote:
>>>
 Hi,

 I would be in favor of dropping Java 7 as we don't use it in our
> hadoop
 infra (and we are a bank). Also, Spark 2.2 has been released today,
 which doesn't
 support Java 7  ses/spark-release-2-2-0.
>> html
>
 anymore, and Flink should not lack behind :-)

 Cheers, Fokko

 2017-07-12 15:56 GMT+02:00 Stephan Ewen :

> Bumping this thread again.
>
> There are several strong points for dropping Java 7 support,
> apart
>> from
 the
> fact that it is not maintained
>
>   - We could really use the Java 8 default methods feature in
 interfaces to
> evolve the API without breaking backwards compatibility
>
>   - Easier build setup for Scala 2.12 (which requires Java 8),
> no need
 to
> manage the tricky combinations of Java / Scala versions
>
>   - Ability to use vanilla Akka (rather than Flakka) which
> requires
 Java 8.
> - Fewer problems for users that use Akka in the Flink
> applications
> - Flakka currently does not support Scala 2.12
> - Newer Akka versions shade protobuf, which is important
>
> I think these together make a pretty good case for bumping the
>> required
> Java version to Java 8.
>
> It would just help both Flink users (dependency management, Scala
 versions)
> and developers (build simplification) a lot.
> Unless we see users stepping forward and making a case that it
> will be
> impossible for them to upgrade to Java 8, I suggest to go
> forward with
> this.
>
> Best,
> Stephan
>
>
>
> On Thu, Jun 8, 2017 at 9:36 PM, Haohui Mai 
>> wrote:
>
>> +1
>>
>> There are several high impacts security vulnerabilities in JDK
> 7 and
 will
>> not be addressed.
>>
>> As a result we completely moved away from JDK 7.
>>
>> +1 on separating the tasks of supporting Scala 2.12 and JDK 8
> in two
> steps.
>>
>>
>> On Thu, Jun 8, 2017 at 9:53 AM Greg Hogan 
>> wrote:
>>
>>> Is this not two different issues?
>>> - adding builds for Scala 2.12
>>> - upgrading to Java version 1.8
>>>
>>> It may be time to switch, but I haven’t seen anything in
>> FLINK-5005
> which
>>> prevents simply adding Scala 2.12 to our supported build
> matrix
>> and
>>> continuing to build 2.10 / 2.11 against Java 1.7.
>>>
>>> Greg
>>>
>>>
 On Jun 8, 2017, at 11:39 AM, Robert Metzger <
>> rmetz...@apache.org>
>> wrote:

 Hi all,

 as promised in March, I want to revive this discussion!

 Our users are begging for Scala 2.12 support [1],
> migration to
 Akka
> 2.4
>>> would solve a bunch of shading / dependency issues (Akka 2.4
> will
> remove
>>> Akka's 

Re: [POLL] Who still uses Java 7 with Flink ?

[Niels Basjes]

+1 For dropping java 1.7

On 13 Jul 2017 04:11, "Jark Wu"  wrote:

> +1 for dropping Java 7
>
> 2017-07-13 9:34 GMT+08:00 ☼ R Nair (रविशंकर नायर) <
> ravishankar.n...@gmail.com>:
>
>> +1 for dropping Java 1.7.
>>
>> On Wed, Jul 12, 2017 at 9:10 PM, Kurt Young  wrote:
>>
>>> +1 for droppint Java 7, we have been using Java 8 for more than one year
>>> in Alibaba and everything work fine.
>>>
>>> Best,
>>> Kurt
>>>
>>> On Thu, Jul 13, 2017 at 2:53 AM, Bowen Li 
>>> wrote:
>>>
 +1 for dropping Java 7

 On Wed, Jul 12, 2017 at 9:04 AM, Gyula Fóra 
 wrote:

 > +1 for dropping 1.7 from me as well.
 >
 > Gyula
 >
 > On Wed, Jul 12, 2017, 17:53 Ted Yu  wrote:
 >
 > > +1 on dropping support for Java 1.7
 > >
 > >  Original message 
 > > From: Robert Metzger 
 > > Date: 7/12/17 8:36 AM (GMT-08:00)
 > > To: dev@flink.apache.org
 > > Cc: user 
 > > Subject: Re: [POLL] Who still uses Java 7 with Flink ?
 > >
 > > +1 to drop Java 7 support
 > >
 > > I believe that we can move to Java 8 for the argument you've stated.
 > > ElasticSearch 5, Spark 2.2  require Java 8 already, Hadoop 3.0.0
 will
 > > require it as well.
 > >
 > > On Wed, Jul 12, 2017 at 4:02 PM, Driesprong, Fokko
  >
 > > wrote:
 > >
 > >> Hi,
 > >>
 > >> I would be in favor of dropping Java 7 as we don't use it in our
 hadoop
 > >> infra (and we are a bank). Also, Spark 2.2 has been released today,
 > >> which doesn't
 > >> support Java 7  html
 > >> >
 > >> anymore, and Flink should not lack behind :-)
 > >>
 > >> Cheers, Fokko
 > >>
 > >> 2017-07-12 15:56 GMT+02:00 Stephan Ewen :
 > >>
 > >> > Bumping this thread again.
 > >> >
 > >> > There are several strong points for dropping Java 7 support,
 apart
 > from
 > >> the
 > >> > fact that it is not maintained
 > >> >
 > >> >   - We could really use the Java 8 default methods feature in
 > >> interfaces to
 > >> > evolve the API without breaking backwards compatibility
 > >> >
 > >> >   - Easier build setup for Scala 2.12 (which requires Java 8),
 no need
 > >> to
 > >> > manage the tricky combinations of Java / Scala versions
 > >> >
 > >> >   - Ability to use vanilla Akka (rather than Flakka) which
 requires
 > >> Java 8.
 > >> > - Fewer problems for users that use Akka in the Flink
 applications
 > >> > - Flakka currently does not support Scala 2.12
 > >> > - Newer Akka versions shade protobuf, which is important
 > >> >
 > >> > I think these together make a pretty good case for bumping the
 > required
 > >> > Java version to Java 8.
 > >> >
 > >> > It would just help both Flink users (dependency management, Scala
 > >> versions)
 > >> > and developers (build simplification) a lot.
 > >> > Unless we see users stepping forward and making a case that it
 will be
 > >> > impossible for them to upgrade to Java 8, I suggest to go
 forward with
 > >> > this.
 > >> >
 > >> > Best,
 > >> > Stephan
 > >> >
 > >> >
 > >> >
 > >> > On Thu, Jun 8, 2017 at 9:36 PM, Haohui Mai 
 > wrote:
 > >> >
 > >> > > +1
 > >> > >
 > >> > > There are several high impacts security vulnerabilities in JDK
 7 and
 > >> will
 > >> > > not be addressed.
 > >> > >
 > >> > > As a result we completely moved away from JDK 7.
 > >> > >
 > >> > > +1 on separating the tasks of supporting Scala 2.12 and JDK 8
 in two
 > >> > steps.
 > >> > >
 > >> > >
 > >> > > On Thu, Jun 8, 2017 at 9:53 AM Greg Hogan 
 > wrote:
 > >> > >
 > >> > > > Is this not two different issues?
 > >> > > > - adding builds for Scala 2.12
 > >> > > > - upgrading to Java version 1.8
 > >> > > >
 > >> > > > It may be time to switch, but I haven’t seen anything in
 > FLINK-5005
 > >> > which
 > >> > > > prevents simply adding Scala 2.12 to our supported build
 matrix
 > and
 > >> > > > continuing to build 2.10 / 2.11 against Java 1.7.
 > >> > > >
 > >> > > > Greg
 > >> > > >
 > >> > > >
 > >> > > > > On Jun 8, 2017, at 11:39 AM, Robert Metzger <
 > rmetz...@apache.org>
 > >> > > wrote:
 > >> > > > >
 > >> > > > > Hi all,
 > >> > > > >
 > >> > > > > as promised in March, I want to revive this discussion!
 > >> > > > >
 > >> > > > > Our users are begging for Scala 2.12 support [1],
 migration to
 > >> Akka
 > >> > 2.4
 > 

Re: [DISCUSS] Release 1.3.2 planning

[Bowen Li]

Hi Aljoscha,
I'd like to see https://issues.apache.org/jira/browse/FLINK-6951 fixed
in 1.3.2, if it makes sense.

Thanks,
Bowen

On Wed, Jul 12, 2017 at 3:06 AM, Aljoscha Krettek 
wrote:

> Short update, we resolved some blockers and discovered some new ones.
> There’s this nifty Jira page if you want to keep track:
> https://issues.apache.org/jira/projects/FLINK/versions/12340984 <
> https://issues.apache.org/jira/projects/FLINK/versions/12340984>
>
> Once again, could everyone please update the Jira issues that they think
> should be release blocking. I would like to start building release
> candidates at the end of this week, if possible.
>
> And yes, I’m volunteering to be the release manager on this release. ;-)
>
> Best,
> Aljoscha
>
> > On 7. Jul 2017, at 16:03, Aljoscha Krettek  wrote:
> >
> > I think we might have another blocker: https://issues.apache.org/
> jira/browse/FLINK-7133 
> >
> >> On 7. Jul 2017, at 09:18, Haohui Mai  wrote:
> >>
> >> I think we are pretty close now -- Jira shows that we're down to two
> >> blockers: FLINK-7069 and FLINK-6965.
> >>
> >> FLINK-7069 is being merged and we have a PR for FLINK-6965.
> >>
> >> ~Haohui
> >>
> >> On Thu, Jul 6, 2017 at 1:44 AM Aljoscha Krettek 
> wrote:
> >>
> >>> I’m seeing these remaining blockers:
> >>> https://issues.apache.org/jira/browse/FLINK-7069?filter=
> 12334772=project%20%3D%20FLINK%20AND%20priority%20%3D%20Blocker%20AND%
> 20resolution%20%3D%20Unresolved
> >>> <
> >>> https://issues.apache.org/jira/browse/FLINK-7069?filter=
> 12334772=project%20=%20FLINK%20AND%20priority%20=%
> 20Blocker%20AND%20resolution%20=%20Unresolved
> 
> >>>
> >>> Could everyone please correctly mark as “blocking” those issues that
> they
> >>> consider blocking for 1.3.2 so that we get an accurate overview of
> where we
> >>> are.
> >>>
> >>> @Chesnay, could you maybe check if this one should in fact be
> considered a
> >>> blocker: https://issues.apache.org/jira/browse/FLINK-7034? <
> >>> https://issues.apache.org/jira/browse/FLINK-7034?>
> >>>
> >>> Best,
> >>> Aljoscha
>  On 6. Jul 2017, at 07:19, Tzu-Li (Gordon) Tai 
> >>> wrote:
> 
>  FLINK-7041 has been merged.
>  I’d also like to raise another blocker for 1.3.2:
> >>> https://issues.apache.org/jira/browse/FLINK-6996.
> 
>  Cheers,
>  Gordon
>  On 30 June 2017 at 12:46:07 AM, Aljoscha Krettek (aljos...@apache.org
> )
> >>> wrote:
> 
>  Gordon and I found this (in my opinion) blocking issue:
> >>> https://issues.apache.org/jira/browse/FLINK-7041 <
> >>> https://issues.apache.org/jira/browse/FLINK-7041>
> 
>  I’m trying to quickly provide a fix.
> 
> > On 26. Jun 2017, at 15:30, Timo Walther  wrote:
> >
> > I just opened a PR which should be included in the next bug fix
> release
> >>> for the Table API:
> > https://issues.apache.org/jira/browse/FLINK-7005
> >
> > Timo
> >
> > Am 23.06.17 um 14:09 schrieb Robert Metzger:
> >> Thanks Haohui.
> >>
> >> The first main task for the release management is to come up with a
> >> timeline :)
> >> Lets just wait and see which issues get reported. There are
> currently
> >>> no
> >> blockers set for 1.3.1 in JIRA.
> >>
> >> On Thu, Jun 22, 2017 at 6:47 PM, Haohui Mai 
> >>> wrote:
> >>
> >>> Hi,
> >>>
> >>> Release management is though, I'm happy to help. Are there any
> >>> timelines
> >>> you have in mind?
> >>>
> >>> Haohui
> >>> On Fri, Jun 23, 2017 at 12:01 AM Robert Metzger <
> rmetz...@apache.org>
> >>> wrote:
> >>>
>  Hi all,
> 
>  with the 1.3.1 release on the way, we can start thinking about the
> >>> 1.3.2
>  release.
> 
>  We have already one issue that should go in there:
>  - https://issues.apache.org/jira/browse/FLINK-6964
> 
>  If there are any other blockers, let us know here :)
> 
>  I'm wondering if there's somebody from the community who's
> willing to
> >>> take
>  care of the release management of 1.3.2 :)
> 
> >
> 
> >>>
> >>>
> >
>
>