[jira] [Commented] (FLINK-8519) FileAlreadyExistsException on Start Flink Session
[
https://issues.apache.org/jira/browse/FLINK-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406435#comment-16406435
]
Hai Zhou UTC+8 commented on FLINK-8519:
---
[~aljoscha] [~NicoK] , I am sorry for the late reply.
I found the reason for the issue.
when build flink from source, it needs to specify that \{{hadoop.version}} is a
version maintained by our company.
;)
> FileAlreadyExistsException on Start Flink Session
> --
>
> Key: FLINK-8519
> URL: https://issues.apache.org/jira/browse/FLINK-8519
> Project: Flink
> Issue Type: Bug
> Components: YARN
>Affects Versions: 1.5.0
>Reporter: Hai Zhou UTC+8
>Priority: Blocker
> Fix For: 1.5.0
>
>
> *steps to reproduce:*
> 1. build flink from source , git commit: c1734f4
> 2. run script:
> source /path/hadoop/bin/hadoop_user_login.sh hadoop-launcher;
> export YARN_CONF_DIR=/path/hadoop/etc/hadoop;
> export HADOOP_CONF_DIR=/path/hadoop/etc/hadoop;
> export JVM_ARGS="-Djava.security.krb5.conf=${HADOOP_CONF_DIR}/krb5.conf";
> /path/flink-1.5-SNAPSHOT/bin/yarn-session.sh -D
> yarn.container-start-command-template="/usr/local/jdk1.8.0_112/bin/java
> %%jvmmem%% %%jvmopts%% %%logging%% %%class%% %%args%% %%redirects%%" -n 4 -nm
> job_name -qu root.rt.flink -jm 1024 -tm 4096 -s 4 -d
>
> *error infos:*
> 2018-01-27 00:51:12,841 ERROR org.apache.flink.yarn.cli.FlinkYarnSessionCli -
> Error while running the Flink Yarn session.
> java.lang.reflect.UndeclaredThrowableException
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1571)
> at
> org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSecurityContext.java:41)
> at
> org.apache.flink.yarn.cli.FlinkYarnSessionCli.main(FlinkYarnSessionCli.java:786)
> Caused by: org.apache.flink.client.deployment.ClusterDeploymentException:
> Couldn't deploy Yarn session cluster
> at
> org.apache.flink.yarn.AbstractYarnClusterDescriptor.deploySessionCluster(AbstractYarnClusterDescriptor.java:389)
> at
> org.apache.flink.yarn.cli.FlinkYarnSessionCli.run(FlinkYarnSessionCli.java:594)
> at
> org.apache.flink.yarn.cli.FlinkYarnSessionCli.lambda$main$2(FlinkYarnSessionCli.java:786)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1556)
> ... 2 more
> Caused by: org.apache.hadoop.fs.FileAlreadyExistsException: Path /user
> already exists as dir; cannot create link here
> at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:244)
> at org.apache.hadoop.fs.viewfs.InodeTree.(InodeTree.java:334)
> at
> org.apache.hadoop.fs.viewfs.ViewFileSystem$1.(ViewFileSystem.java:161)
> at
> org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:161)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2397)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:89)
> at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2431)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2413)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:368)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:167)
> at
> org.apache.flink.yarn.AbstractYarnClusterDescriptor.startAppMaster(AbstractYarnClusterDescriptor.java:656)
> at
> org.apache.flink.yarn.AbstractYarnClusterDescriptor.deployInternal(AbstractYarnClusterDescriptor.java:485)
> at
> org.apache.flink.yarn.AbstractYarnClusterDescriptor.deploySessionCluster(AbstractYarnClusterDescriptor.java:384)
> ... 7 more
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (FLINK-8313) Please add REAMD file for flink-web repository
[
https://issues.apache.org/jira/browse/FLINK-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 closed FLINK-8313.
-
Resolution: Won't Fix
> Please add REAMD file for flink-web repository
> --
>
> Key: FLINK-8313
> URL: https://issues.apache.org/jira/browse/FLINK-8313
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
>Reporter: Hai Zhou UTC+8
>Priority: Major
>
> Add a REAMD file to Introduce:
> 1、What's the {{flink-web}} repository
> 2、How to Contribute it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FLINK-8519) FileAlreadyExistsException on Start Flink Session
Hai Zhou UTC+8 created FLINK-8519:
-
Summary: FileAlreadyExistsException on Start Flink Session
Key: FLINK-8519
URL: https://issues.apache.org/jira/browse/FLINK-8519
Project: Flink
Issue Type: Bug
Components: YARN
Affects Versions: 1.5.0
Reporter: Hai Zhou UTC+8
Fix For: 1.5.0
*steps to reproduce:*
1. build flink from source , git commit: c1734f4
2. run script:
source /path/hadoop/bin/hadoop_user_login.sh hadoop-launcher;
export YARN_CONF_DIR=/path/hadoop/etc/hadoop;
export HADOOP_CONF_DIR=/path/hadoop/etc/hadoop;
export JVM_ARGS="-Djava.security.krb5.conf=${HADOOP_CONF_DIR}/krb5.conf";
/path/flink-1.5-SNAPSHOT/bin/yarn-session.sh -D
yarn.container-start-command-template="/usr/local/jdk1.8.0_112/bin/java
%%jvmmem%% %%jvmopts%% %%logging%% %%class%% %%args%% %%redirects%%" -n 4 -nm
job_name -qu root.rt.flink -jm 1024 -tm 4096 -s 4 -d
*error infos:*
2018-01-27 00:51:12,841 ERROR org.apache.flink.yarn.cli.FlinkYarnSessionCli -
Error while running the Flink Yarn session.
java.lang.reflect.UndeclaredThrowableException
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1571)
at
org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSecurityContext.java:41)
at
org.apache.flink.yarn.cli.FlinkYarnSessionCli.main(FlinkYarnSessionCli.java:786)
Caused by: org.apache.flink.client.deployment.ClusterDeploymentException:
Couldn't deploy Yarn session cluster
at
org.apache.flink.yarn.AbstractYarnClusterDescriptor.deploySessionCluster(AbstractYarnClusterDescriptor.java:389)
at
org.apache.flink.yarn.cli.FlinkYarnSessionCli.run(FlinkYarnSessionCli.java:594)
at
org.apache.flink.yarn.cli.FlinkYarnSessionCli.lambda$main$2(FlinkYarnSessionCli.java:786)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1556)
... 2 more
Caused by: org.apache.hadoop.fs.FileAlreadyExistsException: Path /user already
exists as dir; cannot create link here
at org.apache.hadoop.fs.viewfs.InodeTree.createLink(InodeTree.java:244)
at org.apache.hadoop.fs.viewfs.InodeTree.(InodeTree.java:334)
at org.apache.hadoop.fs.viewfs.ViewFileSystem$1.(ViewFileSystem.java:161)
at
org.apache.hadoop.fs.viewfs.ViewFileSystem.initialize(ViewFileSystem.java:161)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2397)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:89)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2431)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2413)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:368)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:167)
at
org.apache.flink.yarn.AbstractYarnClusterDescriptor.startAppMaster(AbstractYarnClusterDescriptor.java:656)
at
org.apache.flink.yarn.AbstractYarnClusterDescriptor.deployInternal(AbstractYarnClusterDescriptor.java:485)
at
org.apache.flink.yarn.AbstractYarnClusterDescriptor.deploySessionCluster(AbstractYarnClusterDescriptor.java:384)
... 7 more
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FLINK-7980) Bump joda-time to 2.9.9
[ https://issues.apache.org/jira/browse/FLINK-7980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342038#comment-16342038 ] Hai Zhou UTC+8 commented on FLINK-7980: --- agree. :) I will work FLINK-7344:Migrate usage of joda-time to the Java 8 DateTime API. > Bump joda-time to 2.9.9 > --- > > Key: FLINK-7980 > URL: https://issues.apache.org/jira/browse/FLINK-7980 > Project: Flink > Issue Type: Improvement > Components: Build System >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Major > Fix For: 1.5.0 > > > joda-time is version 2.5(Oct, 2014), bumping to 2.9.9(the latest version). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLINK-7980) Bump joda-time to 2.9.9
[ https://issues.apache.org/jira/browse/FLINK-7980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7980. - Resolution: Won't Fix > Bump joda-time to 2.9.9 > --- > > Key: FLINK-7980 > URL: https://issues.apache.org/jira/browse/FLINK-7980 > Project: Flink > Issue Type: Improvement > Components: Build System >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Major > Fix For: 1.5.0 > > > joda-time is version 2.5(Oct, 2014), bumping to 2.9.9(the latest version). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLINK-7344) Migrate usage of joda-time to the Java 8 DateTime API
[ https://issues.apache.org/jira/browse/FLINK-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7344: - Assignee: Hai Zhou UTC+8 (was: Haohui Mai) > Migrate usage of joda-time to the Java 8 DateTime API > - > > Key: FLINK-7344 > URL: https://issues.apache.org/jira/browse/FLINK-7344 > Project: Flink > Issue Type: Improvement > Components: Core >Reporter: Haohui Mai >Assignee: Hai Zhou UTC+8 >Priority: Major > > As the minimum Java version of Flink has been upgraded to 1.8, it is a good > time to migrate all usage of the joda-time package to the native Java 8 > DateTime API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLINK-7604) Add OpenTSDB metrics reporter
[ https://issues.apache.org/jira/browse/FLINK-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7604. - Resolution: Won't Do Fix Version/s: (was: 1.5.0) > Add OpenTSDB metrics reporter > - > > Key: FLINK-7604 > URL: https://issues.apache.org/jira/browse/FLINK-7604 > Project: Flink > Issue Type: Bug > Components: Metrics >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-8359) Update copyright date in NOTICE
Hai Zhou UTC+8 created FLINK-8359: - Summary: Update copyright date in NOTICE Key: FLINK-8359 URL: https://issues.apache.org/jira/browse/FLINK-8359 Project: Flink Issue Type: Task Components: Build System Affects Versions: 1.5.0 Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Fix For: 1.5.0 NOTICE file has copyright year as 2014-2017. This needs to be updated as 2014-2018. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-8313) Please add REAMD file for flink-web repository
[
https://issues.apache.org/jira/browse/FLINK-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302373#comment-16302373
]
Hai Zhou UTC+8 commented on FLINK-8313:
---
BTW, The default branch of the {{flink-web}} repository was modified from
{{asf-site}} to {{master}}.
> Please add REAMD file for flink-web repository
> --
>
> Key: FLINK-8313
> URL: https://issues.apache.org/jira/browse/FLINK-8313
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
>Reporter: Hai Zhou UTC+8
>
> Add a REAMD file to Introduce:
> 1、What's the {{flink-web}} repository
> 2、How to Contribute it
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-8313) Please add REAMD file for flink-web repository
Hai Zhou UTC+8 created FLINK-8313:
-
Summary: Please add REAMD file for flink-web repository
Key: FLINK-8313
URL: https://issues.apache.org/jira/browse/FLINK-8313
Project: Flink
Issue Type: Improvement
Components: Project Website
Reporter: Hai Zhou UTC+8
Add a REAMD file to Introduce:
1、What's the {{flink-web}} repository
2、How to Contribute it
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-8228) Code cleanup - pointless bitwise expressions
Hai Zhou UTC+8 created FLINK-8228: - Summary: Code cleanup - pointless bitwise expressions Key: FLINK-8228 URL: https://issues.apache.org/jira/browse/FLINK-8228 Project: Flink Issue Type: Improvement Components: Checkstyle Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Priority: Trivial Fix For: 1.5.0 Such expressions include anding with zero, oring by zero, and shifting by zero. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-8178) Introduce not threadsafe write only BufferBuilder
[ https://issues.apache.org/jira/browse/FLINK-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-8178: - Assignee: Piotr Nowojski > Introduce not threadsafe write only BufferBuilder > - > > Key: FLINK-8178 > URL: https://issues.apache.org/jira/browse/FLINK-8178 > Project: Flink > Issue Type: Improvement > Components: Network >Reporter: Piotr Nowojski >Assignee: Piotr Nowojski > Fix For: 1.5.0 > > > While Buffer class is used in multithreaded context it requires > synchronisation. Now it is miss-leading/unclear and suggesting that > RecordSerializer should take into account synchronisation of the Buffer > that's holding. With NotThreadSafe BufferBuilder there would be clear > separation between single-threaded writing/creating a BufferBuilder and > multithreaded Buffer handling/retaining/recycling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (FLINK-8167) Failing WikipediaEditsSourceTest on Travis
[
https://issues.apache.org/jira/browse/FLINK-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272233#comment-16272233
]
Hai Zhou UTC+8 edited comment on FLINK-8167 at 11/30/17 6:59 AM:
-
I agree with "move some low popularity connectors to Apache Bahir". about this,
I mentioned a ticket FLINK-7510 before.
BTW, It is very common for test suites or build scripts to hang. Travis CI has
specific time limits for each job, and will stop. {{A job on travis-ci.org
takes longer than 50 minutes, will be stoped.}}
Currently, the "misc" profile mvn script executes very close to 50 minutes and
occasionally builds timeouts.
Do we have a better way to solve this problem?
was (Author: yew1eb):
I agree with "move some low popularity connectors to Apache Bahir". about this,
I mentioned a ticket FLINK-7510 before.
BTW, It is very common for test suites or build scripts to hang. Travis CI has
specific time limits for each job, and will stop. {{A job on travis-ci.org
takes longer than 50 minutes, will be stoped.}}
Currently, the "misc" profile mvn script executes very close to 50 minutes and
occasionally builds timeouts.
We have no better way to solve this problem?
> Failing WikipediaEditsSourceTest on Travis
> --
>
> Key: FLINK-8167
> URL: https://issues.apache.org/jira/browse/FLINK-8167
> Project: Flink
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.5.0
>Reporter: Till Rohrmann
>Assignee: Ufuk Celebi
>Priority: Critical
> Labels: test-stability
> Fix For: 1.5.0
>
>
> I've observed the {{WikipediaEditsSourceTest}} failing on Travis.
> https://travis-ci.org/tillrohrmann/flink/jobs/308351298
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FLINK-8167) Failing WikipediaEditsSourceTest on Travis
[
https://issues.apache.org/jira/browse/FLINK-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272233#comment-16272233
]
Hai Zhou UTC+8 commented on FLINK-8167:
---
I agree with "move some low popularity connectors to Apache Bahir". about this,
I mentioned a ticket FLINK-7510 before.
BTW, It is very common for test suites or build scripts to hang. Travis CI has
specific time limits for each job, and will stop. {{A job on travis-ci.org
takes longer than 50 minutes, will be stoped.}}
Currently, the "misc" profile mvn script executes very close to 50 minutes and
occasionally builds timeouts.
We have no better way to solve this problem?
> Failing WikipediaEditsSourceTest on Travis
> --
>
> Key: FLINK-8167
> URL: https://issues.apache.org/jira/browse/FLINK-8167
> Project: Flink
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.5.0
>Reporter: Till Rohrmann
>Assignee: Ufuk Celebi
>Priority: Critical
> Labels: test-stability
> Fix For: 1.5.0
>
>
> I've observed the {{WikipediaEditsSourceTest}} failing on Travis.
> https://travis-ci.org/tillrohrmann/flink/jobs/308351298
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FLINK-7762) Make WikipediaEditsSourceTest a proper test
[
https://issues.apache.org/jira/browse/FLINK-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16270974#comment-16270974
]
Hai Zhou UTC+8 commented on FLINK-7762:
---
Hi [~uce], yes. If you want, then you can work on it.
> Make WikipediaEditsSourceTest a proper test
> ---
>
> Key: FLINK-7762
> URL: https://issues.apache.org/jira/browse/FLINK-7762
> Project: Flink
> Issue Type: Improvement
> Components: Streaming Connectors
>Reporter: Aljoscha Krettek
>Assignee: Ufuk Celebi
>Priority: Minor
>
> {{WikipediaEditsSourceTest}} is currently an ITCase even though it's called
> test. Making it a test reduces runtime and also makes it more stable because
> we don't run a whole Flink job.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-7777) Bump japicmp to 0.11.0
[
https://issues.apache.org/jira/browse/FLINK-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 updated FLINK-:
--
Affects Version/s: (was: 1.3.2)
1.5.0
> Bump japicmp to 0.11.0
> --
>
> Key: FLINK-
> URL: https://issues.apache.org/jira/browse/FLINK-
> Project: Flink
> Issue Type: Bug
> Components: Build System
>Affects Versions: 1.5.0
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
>Priority: Minor
> Fix For: 1.5.0
>
>
> Currently, flink used japicmp-maven-plugin version is 0.7.0, I'm getting
> these warnings from the maven plugin during a *mvn clean verify*:
> {code:java}
> [INFO] Written file '.../target/japicmp/japicmp.diff'.
> [INFO] Written file '.../target/japicmp/japicmp.xml'.
> [INFO] Written file '.../target/japicmp/japicmp.html'.
> Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> Compiler warnings:
> WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property
> 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
> Warning: org.apache.xerces.parsers.SAXParser: Feature
> 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Property
> 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> {code}
> japicmp fixed in version 0.7.1 : _Excluded xerces vom maven-reporting
> dependency in order to prevent warnings from SAXParserImpl. _
> The current stable version is 0.11.0, we can consider upgrading to this
> version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-8156) Bump commons-beanutils version to 1.9.3
Hai Zhou UTC+8 created FLINK-8156:
-
Summary: Bump commons-beanutils version to 1.9.3
Key: FLINK-8156
URL: https://issues.apache.org/jira/browse/FLINK-8156
Project: Flink
Issue Type: Bug
Components: Build System
Affects Versions: 1.4.0
Reporter: Hai Zhou UTC+8
Assignee: Hai Zhou UTC+8
Fix For: 1.5.0
Commons-beanutils v1.8.0 dependency is not security compliant. See
[CVE-2014-0114|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114]:
{noformat}
Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in
Apache Struts 1.x through 1.3.10 and in other products requiring
commons-beanutils through 1.9.2, does not suppress the class property, which
allows remote attackers to "manipulate" the ClassLoader and execute arbitrary
code via the class parameter, as demonstrated by the passing of this parameter
to the getClass method of the ActionForm object in Struts 1.
{noformat}
Note that current version commons-beanutils 1.9.2 in turn has a CVE in its
dependency commons-collections (CVE-2015-6420, see BEANUTILS-488), which is
fixed in 1.9.3.
We should upgrade {{commons-beanutils}} from 1.8.3 to 1.9.3
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-8156) Bump commons-beanutils version to 1.9.3
[
https://issues.apache.org/jira/browse/FLINK-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 updated FLINK-8156:
--
Description:
Commons-beanutils v1.8.0 dependency is not security compliant. See
[CVE-2014-0114|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114]:
{code:java}
Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in
Apache Struts 1.x through 1.3.10 and in other products requiring
commons-beanutils through 1.9.2, does not suppress the class property, which
allows remote attackers to "manipulate" the ClassLoader and execute arbitrary
code via the class parameter, as demonstrated by the passing of this parameter
to the getClass method of the ActionForm object in Struts 1.
{code}
Note that current version commons-beanutils 1.9.2 in turn has a CVE in its
dependency commons-collections (CVE-2015-6420, see BEANUTILS-488), which is
fixed in 1.9.3.
We should upgrade {{commons-beanutils}} from 1.8.3 to 1.9.3
was:
Commons-beanutils v1.8.0 dependency is not security compliant. See
[CVE-2014-0114|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114]:
{noformat}
Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in
Apache Struts 1.x through 1.3.10 and in other products requiring
commons-beanutils through 1.9.2, does not suppress the class property, which
allows remote attackers to "manipulate" the ClassLoader and execute arbitrary
code via the class parameter, as demonstrated by the passing of this parameter
to the getClass method of the ActionForm object in Struts 1.
{noformat}
Note that current version commons-beanutils 1.9.2 in turn has a CVE in its
dependency commons-collections (CVE-2015-6420, see BEANUTILS-488), which is
fixed in 1.9.3.
We should upgrade {{commons-beanutils}} from 1.8.3 to 1.9.3
> Bump commons-beanutils version to 1.9.3
> ---
>
> Key: FLINK-8156
> URL: https://issues.apache.org/jira/browse/FLINK-8156
> Project: Flink
> Issue Type: Bug
> Components: Build System
>Affects Versions: 1.4.0
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
> Fix For: 1.5.0
>
>
> Commons-beanutils v1.8.0 dependency is not security compliant. See
> [CVE-2014-0114|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114]:
> {code:java}
> Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar
> in Apache Struts 1.x through 1.3.10 and in other products requiring
> commons-beanutils through 1.9.2, does not suppress the class property, which
> allows remote attackers to "manipulate" the ClassLoader and execute arbitrary
> code via the class parameter, as demonstrated by the passing of this
> parameter to the getClass method of the ActionForm object in Struts 1.
> {code}
> Note that current version commons-beanutils 1.9.2 in turn has a CVE in its
> dependency commons-collections (CVE-2015-6420, see BEANUTILS-488), which is
> fixed in 1.9.3.
> We should upgrade {{commons-beanutils}} from 1.8.3 to 1.9.3
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-7982) Bump commons-configuration to 2.2
[
https://issues.apache.org/jira/browse/FLINK-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 updated FLINK-7982:
--
Summary: Bump commons-configuration to 2.2 (was: Bump
commons-configuration to 2.1.1)
> Bump commons-configuration to 2.2
> -
>
> Key: FLINK-7982
> URL: https://issues.apache.org/jira/browse/FLINK-7982
> Project: Flink
> Issue Type: Improvement
> Components: Build System
>Affects Versions: 1.4.0
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
> Fix For: 1.5.0
>
>
> Currently the dependency
> {{org.apache.commons:commons-configuration (version:1.7, Sep, 2011)}},
> update to
> {{org.apache.commons: commons-configuration2: 2.1.1}}
> Reference hadoop:
> [Hadoop Commom: HADOOP-14648 - Bump commons-configuration2 to
> 2.1.1|https://issues.apache.org/jira/browse/HADOOP-14648]
> [Hadoop Common: HADOOP-13660 - Upgrade commons-configuration version to
> 2.1|https://issues.apache.org/jira/browse/HADOOP-13660]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-7982) Bump commons-configuration to 2.2
[
https://issues.apache.org/jira/browse/FLINK-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 updated FLINK-7982:
--
Description:
Currently the dependency
{{org.apache.commons:commons-configuration (version:1.7, Sep, 2011)}},
update to
{{org.apache.commons: commons-configuration2: 2.2}}
Reference hadoop:
[Hadoop Commom: HADOOP-14648 - Bump commons-configuration2 to
2.1.1|https://issues.apache.org/jira/browse/HADOOP-14648]
[Hadoop Common: HADOOP-13660 - Upgrade commons-configuration version to
2.1|https://issues.apache.org/jira/browse/HADOOP-13660]
was:
Currently the dependency
{{org.apache.commons:commons-configuration (version:1.7, Sep, 2011)}},
update to
{{org.apache.commons: commons-configuration2: 2.1.1}}
Reference hadoop:
[Hadoop Commom: HADOOP-14648 - Bump commons-configuration2 to
2.1.1|https://issues.apache.org/jira/browse/HADOOP-14648]
[Hadoop Common: HADOOP-13660 - Upgrade commons-configuration version to
2.1|https://issues.apache.org/jira/browse/HADOOP-13660]
> Bump commons-configuration to 2.2
> -
>
> Key: FLINK-7982
> URL: https://issues.apache.org/jira/browse/FLINK-7982
> Project: Flink
> Issue Type: Improvement
> Components: Build System
>Affects Versions: 1.4.0
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
> Fix For: 1.5.0
>
>
> Currently the dependency
> {{org.apache.commons:commons-configuration (version:1.7, Sep, 2011)}},
> update to
> {{org.apache.commons: commons-configuration2: 2.2}}
> Reference hadoop:
> [Hadoop Commom: HADOOP-14648 - Bump commons-configuration2 to
> 2.1.1|https://issues.apache.org/jira/browse/HADOOP-14648]
> [Hadoop Common: HADOOP-13660 - Upgrade commons-configuration version to
> 2.1|https://issues.apache.org/jira/browse/HADOOP-13660]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (FLINK-3829) flink-java
[
https://issues.apache.org/jira/browse/FLINK-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 reassigned FLINK-3829:
-
Assignee: Hai Zhou UTC+8
> flink-java
> --
>
> Key: FLINK-3829
> URL: https://issues.apache.org/jira/browse/FLINK-3829
> Project: Flink
> Issue Type: Sub-task
> Components: Build System
>Reporter: Till Rohrmann
>Assignee: Hai Zhou UTC+8
>
> {noformat}
> [WARNING] Used undeclared dependencies found:
> [WARNING]com.esotericsoftware.kryo:kryo:jar:2.24.0:compile
> [WARNING]commons-cli:commons-cli:jar:1.3.1:compile
> [WARNING]org.apache.flink:flink-metrics-core:jar:1.4-SNAPSHOT:compile
> [WARNING]org.hamcrest:hamcrest-core:jar:1.3:test
> [WARNING]org.apache.flink:flink-annotations:jar:1.4-SNAPSHOT:compile
> [WARNING] Unused declared dependencies found:
> [WARNING]org.hamcrest:hamcrest-all:jar:1.3:test
> [WARNING]org.powermock:powermock-module-junit4:jar:1.6.5:test
> [WARNING]com.google.code.findbugs:jsr305:jar:1.3.9:compile
> [WARNING]log4j:log4j:jar:1.2.17:test
> [WARNING]org.powermock:powermock-api-mockito:jar:1.6.5:test
> [WARNING]org.apache.flink:force-shading:jar:1.4-SNAPSHOT:compile
> [WARNING]org.slf4j:slf4j-log4j12:jar:1.7.7:test
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-8149) Replace usages of deprecated SerializationSchema
Hai Zhou UTC+8 created FLINK-8149:
-
Summary: Replace usages of deprecated SerializationSchema
Key: FLINK-8149
URL: https://issues.apache.org/jira/browse/FLINK-8149
Project: Flink
Issue Type: Improvement
Components: Kinesis Connector
Affects Versions: 1.4.0
Reporter: Hai Zhou UTC+8
Assignee: Hai Zhou UTC+8
Fix For: 1.5.0
The deprecated {{SerializationSchema}} in {{flink-streaming-java}}, has been
moved to {{flink-core}}.
But, the deprecate {{SerializationSchema}} is still used in
{{flink-connector-kinesis}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-8142) Cleanup reference to deprecated constants in ConfigConstants
[ https://issues.apache.org/jira/browse/FLINK-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-8142: -- Affects Version/s: 1.4.0 Fix Version/s: 1.5.0 Component/s: Local Runtime > Cleanup reference to deprecated constants in ConfigConstants > > > Key: FLINK-8142 > URL: https://issues.apache.org/jira/browse/FLINK-8142 > Project: Flink > Issue Type: Improvement > Components: Local Runtime >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Minor > Fix For: 1.5.0 > > > ConfigConstants contains several deprecated String constants that are used by > other Flink modules. Those should be cleaned up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-8142) Cleanup reference to deprecated constants in ConfigConstants
Hai Zhou UTC+8 created FLINK-8142: - Summary: Cleanup reference to deprecated constants in ConfigConstants Key: FLINK-8142 URL: https://issues.apache.org/jira/browse/FLINK-8142 Project: Flink Issue Type: Improvement Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Priority: Minor ConfigConstants contains several deprecated String constants that are used by other Flink modules. Those should be cleaned up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7716) Port JobManagerMetricsHandler to new REST endpoint
[
https://issues.apache.org/jira/browse/FLINK-7716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261898#comment-16261898
]
Hai Zhou UTC+8 commented on FLINK-7716:
---
[~gjy] Sorry, I have not had any free time lately to work on this ticket. this
ticket and FLINK-7717 are freely assigned. you can assign yourself if you are
interested in them.
> Port JobManagerMetricsHandler to new REST endpoint
> --
>
> Key: FLINK-7716
> URL: https://issues.apache.org/jira/browse/FLINK-7716
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination, REST, Webfrontend
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: Hai Zhou UTC+8
> Labels: flip-6
> Fix For: 1.5.0
>
>
> Port {{JobManagerMetricsHandler}} to new REST endpoint.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-7984) Bump snappy-java to 1.1.4
[ https://issues.apache.org/jira/browse/FLINK-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7984: -- Description: Upgrade the snappy java version to 1.1.4(the latest, May, 2017). The older version has some issues like memory leak (https://github.com/xerial/snappy-java/issues/91). Snappy Java [Release Notes|https://github.com/xerial/snappy-java/blob/master/Milestone.md] was:Upgrade the snappy java version to 1.1.4(the latest, May, 2017). The older version has some issues like memory leak (https://github.com/xerial/snappy-java/issues/91). > Bump snappy-java to 1.1.4 > - > > Key: FLINK-7984 > URL: https://issues.apache.org/jira/browse/FLINK-7984 > Project: Flink > Issue Type: Improvement > Components: Build System >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Upgrade the snappy java version to 1.1.4(the latest, May, 2017). The older > version has some issues like memory leak > (https://github.com/xerial/snappy-java/issues/91). > Snappy Java [Release > Notes|https://github.com/xerial/snappy-java/blob/master/Milestone.md] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-8105) Removed unnecessary null check
Hai Zhou UTC+8 created FLINK-8105:
-
Summary: Removed unnecessary null check
Key: FLINK-8105
URL: https://issues.apache.org/jira/browse/FLINK-8105
Project: Flink
Issue Type: Improvement
Components: Checkstyle
Affects Versions: 1.4.0
Reporter: Hai Zhou UTC+8
Assignee: Hai Zhou UTC+8
Priority: Minor
Fix For: 1.5.0
eg.
{code:java}
if (value != null && value instanceof String)
{code}
null instanceof String returns false hence replaced the check with
{code:java}
if (value instanceof String)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (FLINK-8101) Elasticsearch 6.x support
[ https://issues.apache.org/jira/browse/FLINK-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-8101: - Assignee: Hai Zhou UTC+8 > Elasticsearch 6.x support > - > > Key: FLINK-8101 > URL: https://issues.apache.org/jira/browse/FLINK-8101 > Project: Flink > Issue Type: New Feature > Components: ElasticSearch Connector >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Recently, elasticsearch 6.0.0 was released: > https://www.elastic.co/blog/elasticsearch-6-0-0-released > The minimum version of ES6 compatible Elasticsearch Java Client is 5.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-8101) Elasticsearch 6.x support
Hai Zhou UTC+8 created FLINK-8101: - Summary: Elasticsearch 6.x support Key: FLINK-8101 URL: https://issues.apache.org/jira/browse/FLINK-8101 Project: Flink Issue Type: New Feature Components: ElasticSearch Connector Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Fix For: 1.5.0 Recently, elasticsearch 6.0.0 was released: https://www.elastic.co/blog/elasticsearch-6-0-0-released The minimum version of ES6 compatible Elasticsearch Java Client is 5.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7777) Bump japicmp to 0.11.0
[
https://issues.apache.org/jira/browse/FLINK-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 updated FLINK-:
--
Description:
Currently, flink used japicmp-maven-plugin version is 0.7.0, I'm getting these
warnings from the maven plugin during a *mvn clean verify*:
{code:java}
[INFO] Written file '.../target/japicmp/japicmp.diff'.
[INFO] Written file '.../target/japicmp/japicmp.xml'.
[INFO] Written file '.../target/japicmp/japicmp.html'.
Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
recognized.
Compiler warnings:
WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning: org.apache.xerces.parsers.SAXParser: Feature
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning: org.apache.xerces.parsers.SAXParser: Property
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning: org.apache.xerces.parsers.SAXParser: Property
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
recognized.
{code}
japicmp fixed in version 0.7.1 : _Excluded xerces vom maven-reporting
dependency in order to prevent warnings from SAXParserImpl. _
The current stable version is 0.11.0, we can consider upgrading to this version.
was:
Currently, flink used japicmp-maven-plugin version is 0.7.0, I'm getting these
warnings from the maven plugin during a *mvn clean verify*:
{code:java}
[INFO] Written file '.../target/japicmp/japicmp.diff'.
[INFO] Written file '.../target/japicmp/japicmp.xml'.
[INFO] Written file '.../target/japicmp/japicmp.html'.
Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
recognized.
Compiler warnings:
WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning: org.apache.xerces.parsers.SAXParser: Feature
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning: org.apache.xerces.parsers.SAXParser: Property
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning: org.apache.xerces.parsers.SAXParser: Property
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
recognized.
{code}
japicmp fixed in version 0.7.1 : _Excluded xerces vom maven-reporting
dependency in order to prevent warnings from SAXParserImpl. _
The current stable version is 0.10.0, we can consider upgrading to this version.
Summary: Bump japicmp to 0.11.0 (was: Bump japicmp to 0.10.0)
> Bump japicmp to 0.11.0
> --
>
> Key: FLINK-
> URL: https://issues.apache.org/jira/browse/FLINK-
> Project: Flink
> Issue Type: Bug
> Components: Build System
>Affects Versions: 1.3.2
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
>Priority: Minor
> Fix For: 1.5.0
>
>
> Currently, flink used japicmp-maven-plugin version is 0.7.0, I'm getting
> these warnings from the maven plugin during a *mvn clean verify*:
> {code:java}
> [INFO] Written file '.../target/japicmp/japicmp.diff'.
> [INFO] Written file '.../target/japicmp/japicmp.xml'.
> [INFO] Written file '.../target/japicmp/japicmp.html'.
> Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> Compiler warnings:
> WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property
> 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
> Warning: org.apache.xerces.parsers.SAXParser: Feature
> 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Property
> 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> {code}
> japicmp fixed in version 0.7.1 : _Excluded xerces vom maven-reporting
> dependency in order to prevent warnings from SAXParserImpl. _
> The current stable version is 0.11.0, we can consider upgrading to this
> version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (FLINK-6235) Broken link in documentation
[ https://issues.apache.org/jira/browse/FLINK-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-6235. - Resolution: Won't Fix > Broken link in documentation > - > > Key: FLINK-6235 > URL: https://issues.apache.org/jira/browse/FLINK-6235 > Project: Flink > Issue Type: Bug > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Rami >Priority: Minor > > https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/index.html#task-chaining-and-resource-groups > The link comes from: > https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/savepoints.html > At the bottom of the page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7717) Port TaskManagerMetricsHandler to new REST endpoint
[
https://issues.apache.org/jira/browse/FLINK-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 reassigned FLINK-7717:
-
Assignee: Hai Zhou UTC+8
> Port TaskManagerMetricsHandler to new REST endpoint
> ---
>
> Key: FLINK-7717
> URL: https://issues.apache.org/jira/browse/FLINK-7717
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination, REST, Webfrontend
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: Hai Zhou UTC+8
> Labels: flip-6
> Fix For: 1.5.0
>
>
> Port {{TaskManagerMetricsHandler}} to new REST endpoint.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (FLINK-7718) Port JobVertixMetricsHandler to new REST endpoint
[
https://issues.apache.org/jira/browse/FLINK-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 reassigned FLINK-7718:
-
Assignee: Hai Zhou UTC+8
> Port JobVertixMetricsHandler to new REST endpoint
> -
>
> Key: FLINK-7718
> URL: https://issues.apache.org/jira/browse/FLINK-7718
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination, REST, Webfrontend
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: Hai Zhou UTC+8
> Labels: flip-6
> Fix For: 1.5.0
>
>
> Port {{JobVertixMetricsHandler}} to new REST endpoint.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (FLINK-7716) Port JobManagerMetricsHandler to new REST endpoint
[
https://issues.apache.org/jira/browse/FLINK-7716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 reassigned FLINK-7716:
-
Assignee: Hai Zhou UTC+8
> Port JobManagerMetricsHandler to new REST endpoint
> --
>
> Key: FLINK-7716
> URL: https://issues.apache.org/jira/browse/FLINK-7716
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination, REST, Webfrontend
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: Hai Zhou UTC+8
> Labels: flip-6
> Fix For: 1.5.0
>
>
> Port {{JobManagerMetricsHandler}} to new REST endpoint.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (FLINK-7718) Port JobVertixMetricsHandler to new REST endpoint
[
https://issues.apache.org/jira/browse/FLINK-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 reassigned FLINK-7718:
-
Assignee: (was: Hai Zhou UTC+8)
> Port JobVertixMetricsHandler to new REST endpoint
> -
>
> Key: FLINK-7718
> URL: https://issues.apache.org/jira/browse/FLINK-7718
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination, REST, Webfrontend
>Reporter: Tzu-Li (Gordon) Tai
> Labels: flip-6
> Fix For: 1.5.0
>
>
> Port {{JobVertixMetricsHandler}} to new REST endpoint.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FLINK-7679) Upgrade maven enforcer plugin to 3.0.0-M1
[
https://issues.apache.org/jira/browse/FLINK-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245251#comment-16245251
]
Hai Zhou UTC+8 commented on FLINK-7679:
---
Yes.
travis green [ FLINK-7679 Upgrade maven enforcer plugin to 3.0.0-M1 |
https://travis-ci.org/yew1eb/flink/builds/299195368].
BTW, I checkout a branch java9(Add oraclejdk9 to travis) to find more
incompatible issues, you can see:
https://travis-ci.org/yew1eb/flink/builds/299199045
> Upgrade maven enforcer plugin to 3.0.0-M1
> -
>
> Key: FLINK-7679
> URL: https://issues.apache.org/jira/browse/FLINK-7679
> Project: Flink
> Issue Type: Sub-task
> Components: Build System
>Reporter: Ted Yu
>Assignee: Hai Zhou UTC+8
>
> I got the following build error against Java 9:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-maven)
> on project flink-parent: Execution enforce-maven of goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/hbase/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/1.4.1/maven-enforcer-plugin-1.4.1.jar
> {code}
> Upgrading maven enforcer plugin to 3.0.0-M1 would get over the above error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FLINK-8033) Build Flink with JDK 9
[ https://issues.apache.org/jira/browse/FLINK-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244309#comment-16244309 ] Hai Zhou UTC+8 commented on FLINK-8033: --- thx [~greghogan], the description has been updated. > Build Flink with JDK 9 > -- > > Key: FLINK-8033 > URL: https://issues.apache.org/jira/browse/FLINK-8033 > Project: Flink > Issue Type: Improvement > Components: Build System >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > This is a JIRA to track all issues that found to make Flink compatible with > Java 9. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-8033) Build Flink with JDK 9
[ https://issues.apache.org/jira/browse/FLINK-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-8033: -- Description: This is a JIRA to track all issues that found to make Flink compatible with Java 9. (was: This is a JIRA to track all issues that found to support Flink on Java 9 in the future.) > Build Flink with JDK 9 > -- > > Key: FLINK-8033 > URL: https://issues.apache.org/jira/browse/FLINK-8033 > Project: Flink > Issue Type: Improvement > Components: Build System >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > This is a JIRA to track all issues that found to make Flink compatible with > Java 9. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7679) Upgrade maven enforcer plugin to 3.0.0-M1
[
https://issues.apache.org/jira/browse/FLINK-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244228#comment-16244228
]
Hai Zhou UTC+8 commented on FLINK-7679:
---
travis failed: https://travis-ci.org/yew1eb/flink/jobs/299125871
> Upgrade maven enforcer plugin to 3.0.0-M1
> -
>
> Key: FLINK-7679
> URL: https://issues.apache.org/jira/browse/FLINK-7679
> Project: Flink
> Issue Type: Sub-task
> Components: Build System
>Reporter: Ted Yu
>Assignee: Hai Zhou UTC+8
>
> I got the following build error against Java 9:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-maven)
> on project flink-parent: Execution enforce-maven of goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/hbase/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/1.4.1/maven-enforcer-plugin-1.4.1.jar
> {code}
> Upgrading maven enforcer plugin to 3.0.0-M1 would get over the above error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (FLINK-7679) Upgrade maven enforcer plugin to 3.0.0-M1
[
https://issues.apache.org/jira/browse/FLINK-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 reassigned FLINK-7679:
-
Assignee: Hai Zhou UTC+8
> Upgrade maven enforcer plugin to 3.0.0-M1
> -
>
> Key: FLINK-7679
> URL: https://issues.apache.org/jira/browse/FLINK-7679
> Project: Flink
> Issue Type: Sub-task
> Components: Build System
>Reporter: Ted Yu
>Assignee: Hai Zhou UTC+8
>
> I got the following build error against Java 9:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-maven)
> on project flink-parent: Execution enforce-maven of goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/hbase/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/1.4.1/maven-enforcer-plugin-1.4.1.jar
> {code}
> Upgrading maven enforcer plugin to 3.0.0-M1 would get over the above error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-7679) Upgrade maven enforcer plugin to 3.0.0-M1
[
https://issues.apache.org/jira/browse/FLINK-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 updated FLINK-7679:
--
Issue Type: Sub-task (was: Bug)
Parent: FLINK-8033
> Upgrade maven enforcer plugin to 3.0.0-M1
> -
>
> Key: FLINK-7679
> URL: https://issues.apache.org/jira/browse/FLINK-7679
> Project: Flink
> Issue Type: Sub-task
> Components: Build System
>Reporter: Ted Yu
>
> I got the following build error against Java 9:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-maven)
> on project flink-parent: Execution enforce-maven of goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/hbase/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/1.4.1/maven-enforcer-plugin-1.4.1.jar
> {code}
> Upgrading maven enforcer plugin to 3.0.0-M1 would get over the above error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-8033) Build Flink with JDK 9
Hai Zhou UTC+8 created FLINK-8033: - Summary: Build Flink with JDK 9 Key: FLINK-8033 URL: https://issues.apache.org/jira/browse/FLINK-8033 Project: Flink Issue Type: Improvement Components: Build System Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Fix For: 1.5.0 This is a JIRA to track all issues that found to support Flink on Java 9 in the future. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7979) Use Log.*(Object, Throwable) overload to log exceptions
[
https://issues.apache.org/jira/browse/FLINK-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 closed FLINK-7979.
-
Resolution: Won't Fix
> Use Log.*(Object, Throwable) overload to log exceptions
> ---
>
> Key: FLINK-7979
> URL: https://issues.apache.org/jira/browse/FLINK-7979
> Project: Flink
> Issue Type: Improvement
>Affects Versions: 1.4.0
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
>Priority: Critical
> Fix For: 1.5.0
>
>
> I found some code that logging an exception, through convert the exception to
> string or call .getMessage. {{.getMessage()}}.
> I think the better way is to use the Logger method overloads which take
> {{`Throwable`}} as a parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (FLINK-7481) Binary search with integer overflow possibility
[ https://issues.apache.org/jira/browse/FLINK-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7481. - Resolution: Won't Fix > Binary search with integer overflow possibility > --- > > Key: FLINK-7481 > URL: https://issues.apache.org/jira/browse/FLINK-7481 > Project: Flink > Issue Type: Bug > Components: Core >Reporter: Baihua Su > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7907) Flink Metrics documentation missing Scala examples
[ https://issues.apache.org/jira/browse/FLINK-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7907: - Assignee: Hai Zhou UTC+8 > Flink Metrics documentation missing Scala examples > -- > > Key: FLINK-7907 > URL: https://issues.apache.org/jira/browse/FLINK-7907 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Colin Williams >Assignee: Hai Zhou UTC+8 >Priority: Minor > > The Flink metrics documentation is missing Scala examples for many of the > metrics types. To be consistent there should be Scala examples for all the > types. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-1317) Add a standalone version of the Flink Plan Visualizer to the Website
[ https://issues.apache.org/jira/browse/FLINK-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-1317. - Resolution: Won't Fix > Add a standalone version of the Flink Plan Visualizer to the Website > > > Key: FLINK-1317 > URL: https://issues.apache.org/jira/browse/FLINK-1317 > Project: Flink > Issue Type: New Feature > Components: Project Website >Reporter: Stephan Ewen >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-1166) Add a QA bot to Flink that is testing pull requests
[
https://issues.apache.org/jira/browse/FLINK-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 closed FLINK-1166.
-
Resolution: Fixed
Assignee: Robert Metzger
> Add a QA bot to Flink that is testing pull requests
> ---
>
> Key: FLINK-1166
> URL: https://issues.apache.org/jira/browse/FLINK-1166
> Project: Flink
> Issue Type: New Feature
> Components: Build System
>Reporter: Robert Metzger
>Assignee: Robert Metzger
>Priority: Minor
> Labels: starter
>
> We should have a QA bot (similar to Hadoop) that is checking incoming pull
> requests for a few things:
> - Changes to user-facing APIs
> - More compiler warnings than before
> - more Javadoc warnings than before
> - change of the number of files in the lib/ directory.
> - unused dependencies
> - {{@author}} tag.
> - guava (and other shaded jars) in the lib/ directory.
> It should be somehow extensible to add new tests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-7979) Use Log.*(Object, Throwable) overload to log exceptions
[
https://issues.apache.org/jira/browse/FLINK-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 updated FLINK-7979:
--
Description:
I found some code that logging an exception, through convert the exception to
string or call .getMessage. {{.getMessage()}}.
I think the better way is to use the Logger method overloads which take
{{`Throwable`}} as a parameter.
was:
I found some code that logging an exception, through convert the exception to
string or call .getMessage. __.getMessage()__.
I think the better way is to use the Logger method overloads which take
__`Throwable`__ as a parameter.
> Use Log.*(Object, Throwable) overload to log exceptions
> ---
>
> Key: FLINK-7979
> URL: https://issues.apache.org/jira/browse/FLINK-7979
> Project: Flink
> Issue Type: Improvement
>Affects Versions: 1.4.0
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
>Priority: Critical
> Fix For: 1.5.0
>
>
> I found some code that logging an exception, through convert the exception to
> string or call .getMessage. {{.getMessage()}}.
> I think the better way is to use the Logger method overloads which take
> {{`Throwable`}} as a parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-7985) Update findbugs-maven-plugin version to 3.0.2
Hai Zhou UTC+8 created FLINK-7985: - Summary: Update findbugs-maven-plugin version to 3.0.2 Key: FLINK-7985 URL: https://issues.apache.org/jira/browse/FLINK-7985 Project: Flink Issue Type: Improvement Components: Build System Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Priority: Major Fix For: 1.5.0 The findbug version used by flink is pretty old (1.3.9). The old version of Findbugs itself have some bugs (like http://sourceforge.net/p/findbugs/bugs/918/, hit by HADOOP-10474). and the latest version 3.0.2 fixed the "Missing test classes" issue (https://github.com/gleclaire/findbugs-maven-plugin/issues/15). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7984) Bump snappy-java to 1.1.4
[ https://issues.apache.org/jira/browse/FLINK-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7984: -- Affects Version/s: 1.4.0 Fix Version/s: 1.5.0 Component/s: Build System > Bump snappy-java to 1.1.4 > - > > Key: FLINK-7984 > URL: https://issues.apache.org/jira/browse/FLINK-7984 > Project: Flink > Issue Type: Improvement > Components: Build System >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Major > Fix For: 1.5.0 > > > Upgrade the snappy java version to 1.1.4(the latest, May, 2017). The older > version has some issues like memory leak > (https://github.com/xerial/snappy-java/issues/91). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7984) Bump snappy-java to 1.1.4
Hai Zhou UTC+8 created FLINK-7984: - Summary: Bump snappy-java to 1.1.4 Key: FLINK-7984 URL: https://issues.apache.org/jira/browse/FLINK-7984 Project: Flink Issue Type: Improvement Reporter: Hai Zhou UTC+8 Priority: Major Upgrade the snappy java version to 1.1.4(the latest, May, 2017). The older version has some issues like memory leak (https://github.com/xerial/snappy-java/issues/91). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7984) Bump snappy-java to 1.1.4
[ https://issues.apache.org/jira/browse/FLINK-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7984: - Assignee: Hai Zhou UTC+8 > Bump snappy-java to 1.1.4 > - > > Key: FLINK-7984 > URL: https://issues.apache.org/jira/browse/FLINK-7984 > Project: Flink > Issue Type: Improvement >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Major > > Upgrade the snappy java version to 1.1.4(the latest, May, 2017). The older > version has some issues like memory leak > (https://github.com/xerial/snappy-java/issues/91). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7983) Bump prometheus java client to 0.1.0
Hai Zhou UTC+8 created FLINK-7983:
-
Summary: Bump prometheus java client to 0.1.0
Key: FLINK-7983
URL: https://issues.apache.org/jira/browse/FLINK-7983
Project: Flink
Issue Type: Wish
Components: Build System
Affects Versions: 1.4.0
Reporter: Hai Zhou UTC+8
Assignee: Hai Zhou UTC+8
Fix For: 1.5.0
Update the dependencies {{io.prometheus:simpleclient*}} version from 0.0.26 to
0.1.0.
the version 0.1.0 have many improvements:
{noformat}
[FEATURE] Support gzip compression for HTTPServer
[FEATURE] Support running HTTPServer in daemon thread
[BUGFIX] Shutdown threadpool on stop() for HTTPServer
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-7982) Bump commons-configuration to 2.1.1
Hai Zhou UTC+8 created FLINK-7982:
-
Summary: Bump commons-configuration to 2.1.1
Key: FLINK-7982
URL: https://issues.apache.org/jira/browse/FLINK-7982
Project: Flink
Issue Type: Improvement
Components: Build System
Affects Versions: 1.4.0
Reporter: Hai Zhou UTC+8
Assignee: Hai Zhou UTC+8
Priority: Major
Fix For: 1.5.0
Currently the dependency
{{org.apache.commons:commons-configuration (version:1.7, Sep, 2011)}},
update to
{{org.apache.commons: commons-configuration2: 2.1.1}}
Reference hadoop:
[Hadoop Commom: HADOOP-14648 - Bump commons-configuration2 to
2.1.1|https://issues.apache.org/jira/browse/HADOOP-14648]
[Hadoop Common: HADOOP-13660 - Upgrade commons-configuration version to
2.1|https://issues.apache.org/jira/browse/HADOOP-13660]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-7981) Bump commons-lang3 version to 3.6
Hai Zhou UTC+8 created FLINK-7981:
-
Summary: Bump commons-lang3 version to 3.6
Key: FLINK-7981
URL: https://issues.apache.org/jira/browse/FLINK-7981
Project: Flink
Issue Type: Improvement
Components: Build System
Affects Versions: 1.4.0
Reporter: Hai Zhou UTC+8
Assignee: Hai Zhou UTC+8
Fix For: 1.5.0
Update commons-lang3 from 3.3.2 to 3.6.
{{SerializationUtils.clone()}} of commons-lang3 (<3.5) has a bug that break
thread safety, which gets stack sometimes caused by race condition of
initializing hash map.
See https://issues.apache.org/jira/browse/LANG-1251.
**other**
[BEAM-2481:Update commons-lang3 dependency to version
3.6|https://issues.apache.org/jira/browse/BEAM-2481]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-7980) Bump joda-time to 2.9.9
Hai Zhou UTC+8 created FLINK-7980: - Summary: Bump joda-time to 2.9.9 Key: FLINK-7980 URL: https://issues.apache.org/jira/browse/FLINK-7980 Project: Flink Issue Type: Improvement Components: Build System Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Priority: Major Fix For: 1.5.0 joda-time is version 2.5(Oct, 2014), bumping to 2.9.9(the latest version). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7979) Use Log.*(Object, Throwable) overload to log exceptions
[ https://issues.apache.org/jira/browse/FLINK-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7979: -- Description: I found some code that logging an exception, through convert the exception to string or call .getMessage. __.getMessage()__. I think the better way is to use the Logger method overloads which take __`Throwable`__ as a parameter. was: I found some code that logging an exception by call __.getMessage()__. I think the better way is to use the Logger method overloads which take __`Throwable`__ as a parameter. > Use Log.*(Object, Throwable) overload to log exceptions > --- > > Key: FLINK-7979 > URL: https://issues.apache.org/jira/browse/FLINK-7979 > Project: Flink > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Critical > Fix For: 1.5.0 > > > I found some code that logging an exception, through convert the exception to > string or call .getMessage. __.getMessage()__. > I think the better way is to use the Logger method overloads which take > __`Throwable`__ as a parameter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7979) Use Log.*(Object, Throwable) overload to log exceptions
[ https://issues.apache.org/jira/browse/FLINK-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7979: -- Description: I found some code that logging an exception by call __.getMessage()__. I think the better way is to use the Logger method overloads which take __`Throwable`__ as a parameter. was: I found some code that logging an exception, it converts the exception to string or call `.getMessage()`. I think the better way is to use the Logger method overloads which take `Throwable` as a parameter. > Use Log.*(Object, Throwable) overload to log exceptions > --- > > Key: FLINK-7979 > URL: https://issues.apache.org/jira/browse/FLINK-7979 > Project: Flink > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Critical > Fix For: 1.5.0 > > > I found some code that logging an exception by call __.getMessage()__. > I think the better way is to use the Logger method overloads which take > __`Throwable`__ as a parameter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7979) Use Log.*(Object, Throwable) overload to log exceptions
Hai Zhou UTC+8 created FLINK-7979: - Summary: Use Log.*(Object, Throwable) overload to log exceptions Key: FLINK-7979 URL: https://issues.apache.org/jira/browse/FLINK-7979 Project: Flink Issue Type: Improvement Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Priority: Critical Fix For: 1.5.0 I found some code that logging an exception, it converts the exception to string or call `.getMessage()`. I think the better way is to use the Logger method overloads which take `Throwable` as a parameter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7964) Add Apache Kafka 1.0 connector
[ https://issues.apache.org/jira/browse/FLINK-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7964: -- Summary: Add Apache Kafka 1.0 connector (was: Add Apache Kafka 1.0.0 connector) > Add Apache Kafka 1.0 connector > -- > > Key: FLINK-7964 > URL: https://issues.apache.org/jira/browse/FLINK-7964 > Project: Flink > Issue Type: Improvement > Components: Kafka Connector >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Major > Fix For: 1.5.0 > > > Kafka 1.0.0 is no mere bump of the version number. The Apache Kafka Project > Management Committee has packed a number of valuable enhancements into the > release. Here is a summary of a few of them: > * Since its introduction in version 0.10, the Streams API has become hugely > popular among Kafka users, including the likes of Pinterest, Rabobank, > Zalando, and The New York Times. In 1.0, the the API continues to evolve at a > healthy pace. To begin with, the builder API has been improved (KIP-120). A > new API has been added to expose the state of active tasks at runtime > (KIP-130). The new cogroup API makes it much easier to deal with partitioned > aggregates with fewer StateStores and fewer moving parts in your code > (KIP-150). Debuggability gets easier with enhancements to the print() and > writeAsText() methods (KIP-160). And if that’s not enough, check out KIP-138 > and KIP-161 too. For more on streams, check out the Apache Kafka Streams > documentation, including some helpful new tutorial videos. > * Operating Kafka at scale requires that the system remain observable, and to > make that easier, we’ve made a number of improvements to metrics. These are > too many to summarize without becoming tedious, but Connect metrics have been > significantly improved (KIP-196), a litany of new health check metrics are > now exposed (KIP-188), and we now have a global topic and partition count > (KIP-168). Check out KIP-164 and KIP-187 for even more. > * We now support Java 9, leading, among other things, to significantly faster > TLS and CRC32C implementations. Over-the-wire encryption will be faster now, > which will keep Kafka fast and compute costs low when encryption is enabled. > * In keeping with the security theme, KIP-152 cleans up the error handling on > Simple Authentication Security Layer (SASL) authentication attempts. > Previously, some authentication error conditions were indistinguishable from > broker failures and were not logged in a clear way. This is cleaner now. > * Kafka can now tolerate disk failures better. Historically, JBOD storage > configurations have not been recommended, but the architecture has > nevertheless been tempting: after all, why not rely on Kafka’s own > replication mechanism to protect against storage failure rather than using > RAID? With KIP-112, Kafka now handles disk failure more gracefully. A single > disk failure in a JBOD broker will not bring the entire broker down; rather, > the broker will continue serving any log files that remain on functioning > disks. > * Since release 0.11.0, the idempotent producer (which is the producer used > in the presence of a transaction, which of course is the producer we use for > exactly-once processing) required max.in.flight.requests.per.connection to be > equal to one. As anyone who has written or tested a wire protocol can attest, > this put an upper bound on throughput. Thanks to KAFKA-5949, this can now be > as large as five, relaxing the throughput constraint quite a bit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7964) Add Apache Kafka 1.0.0 connector
Hai Zhou UTC+8 created FLINK-7964: - Summary: Add Apache Kafka 1.0.0 connector Key: FLINK-7964 URL: https://issues.apache.org/jira/browse/FLINK-7964 Project: Flink Issue Type: Improvement Components: Kafka Connector Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Priority: Major Fix For: 1.5.0 Kafka 1.0.0 is no mere bump of the version number. The Apache Kafka Project Management Committee has packed a number of valuable enhancements into the release. Here is a summary of a few of them: * Since its introduction in version 0.10, the Streams API has become hugely popular among Kafka users, including the likes of Pinterest, Rabobank, Zalando, and The New York Times. In 1.0, the the API continues to evolve at a healthy pace. To begin with, the builder API has been improved (KIP-120). A new API has been added to expose the state of active tasks at runtime (KIP-130). The new cogroup API makes it much easier to deal with partitioned aggregates with fewer StateStores and fewer moving parts in your code (KIP-150). Debuggability gets easier with enhancements to the print() and writeAsText() methods (KIP-160). And if that’s not enough, check out KIP-138 and KIP-161 too. For more on streams, check out the Apache Kafka Streams documentation, including some helpful new tutorial videos. * Operating Kafka at scale requires that the system remain observable, and to make that easier, we’ve made a number of improvements to metrics. These are too many to summarize without becoming tedious, but Connect metrics have been significantly improved (KIP-196), a litany of new health check metrics are now exposed (KIP-188), and we now have a global topic and partition count (KIP-168). Check out KIP-164 and KIP-187 for even more. * We now support Java 9, leading, among other things, to significantly faster TLS and CRC32C implementations. Over-the-wire encryption will be faster now, which will keep Kafka fast and compute costs low when encryption is enabled. * In keeping with the security theme, KIP-152 cleans up the error handling on Simple Authentication Security Layer (SASL) authentication attempts. Previously, some authentication error conditions were indistinguishable from broker failures and were not logged in a clear way. This is cleaner now. * Kafka can now tolerate disk failures better. Historically, JBOD storage configurations have not been recommended, but the architecture has nevertheless been tempting: after all, why not rely on Kafka’s own replication mechanism to protect against storage failure rather than using RAID? With KIP-112, Kafka now handles disk failure more gracefully. A single disk failure in a JBOD broker will not bring the entire broker down; rather, the broker will continue serving any log files that remain on functioning disks. * Since release 0.11.0, the idempotent producer (which is the producer used in the presence of a transaction, which of course is the producer we use for exactly-once processing) required max.in.flight.requests.per.connection to be equal to one. As anyone who has written or tested a wire protocol can attest, this put an upper bound on throughput. Thanks to KAFKA-5949, this can now be as large as five, relaxing the throughput constraint quite a bit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-6885) RMQSource does not support qos, leading to oom
[ https://issues.apache.org/jira/browse/FLINK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-6885: - Assignee: Hai Zhou UTC+8 > RMQSource does not support qos, leading to oom > -- > > Key: FLINK-6885 > URL: https://issues.apache.org/jira/browse/FLINK-6885 > Project: Flink > Issue Type: Bug > Components: RabbitMQ Connector, Streaming Connectors >Reporter: Ruben van Vreeland >Assignee: Hai Zhou UTC+8 >Priority: Minor > Labels: easyfix > Original Estimate: 2h > Remaining Estimate: 2h > > RabbitMQ connector supports qos, limiting the prefetch to a configurable > amout of objects. With the current builder patter that is used by the > RMQSource howver, this cannot be configured, leading to an OOM when enough > objects are prefetched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7952) Add metrics for counting logging events
[ https://issues.apache.org/jira/browse/FLINK-7952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7952: -- Description: It would be useful to track logging events . *impl:* adds event counting via a custom Log4J Appender, this tracks the number of INFO, WARN, ERROR and FATAL logging events. *ref:* hadoop-common: [org.apache.hadoop.log.metrics. EventCounter |https://github.com/apache/hadoop/blob/f67237cbe7bc48a1b9088e990800b37529f1db2a/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/metrics/EventCounter.java] was: It would be useful to track logging events . *impl:* adds event counting via a custom Log4J Appender, this tracks the number of INFO, WARN, ERROR and FATAL logging events. > Add metrics for counting logging events > > > Key: FLINK-7952 > URL: https://issues.apache.org/jira/browse/FLINK-7952 > Project: Flink > Issue Type: Wish > Components: Metrics >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Critical > Fix For: 1.5.0 > > > It would be useful to track logging events . > *impl:* > adds event counting via a custom Log4J Appender, this tracks the number of > INFO, WARN, ERROR and FATAL logging events. > *ref:* > hadoop-common: [org.apache.hadoop.log.metrics. EventCounter > |https://github.com/apache/hadoop/blob/f67237cbe7bc48a1b9088e990800b37529f1db2a/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/metrics/EventCounter.java] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7952) Add metrics for counting logging events
Hai Zhou UTC+8 created FLINK-7952: - Summary: Add metrics for counting logging events Key: FLINK-7952 URL: https://issues.apache.org/jira/browse/FLINK-7952 Project: Flink Issue Type: Wish Components: Metrics Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Priority: Critical Fix For: 1.5.0 It would be useful to track logging events . *impl:* adds event counting via a custom Log4J Appender, this tracks the number of INFO, WARN, ERROR and FATAL logging events. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-6499) Migrate state configuration options
[
https://issues.apache.org/jira/browse/FLINK-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hai Zhou UTC+8 closed FLINK-6499.
-
Resolution: Fixed
> Migrate state configuration options
> ---
>
> Key: FLINK-6499
> URL: https://issues.apache.org/jira/browse/FLINK-6499
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
>Reporter: Chesnay Schepler
>Assignee: Fang Yong
>
> {code}
> /** The default directory for savepoints. */
> @PublicEvolving
> public static final String SAVEPOINT_DIRECTORY_KEY =
> "state.savepoints.dir";
> /** The default directory used for persistent checkpoints. */
> @PublicEvolving
> public static final String CHECKPOINTS_DIRECTORY_KEY =
> "state.checkpoints.dir";
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FLINK-7286) Flink Dashboard fails to display bytes/records received by sources
[ https://issues.apache.org/jira/browse/FLINK-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7286: -- Fix Version/s: (was: 1.4.0) 1.5.0 > Flink Dashboard fails to display bytes/records received by sources > -- > > Key: FLINK-7286 > URL: https://issues.apache.org/jira/browse/FLINK-7286 > Project: Flink > Issue Type: Bug > Components: Webfrontend >Affects Versions: 1.3.1 >Reporter: Elias Levy >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > It appears Flink can't measure the number of bytes read or records produced > by a source (e.g. Kafka source). This is particularly problematic for simple > jobs where the job pipeline is chained, and in which there are no > measurements between operators. Thus, in the UI it appears that the job is > not consuming any data. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7697) Add metrics for Elasticsearch Sink
[ https://issues.apache.org/jira/browse/FLINK-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7697: -- Fix Version/s: 1.5.0 > Add metrics for Elasticsearch Sink > -- > > Key: FLINK-7697 > URL: https://issues.apache.org/jira/browse/FLINK-7697 > Project: Flink > Issue Type: Wish > Components: ElasticSearch Connector >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Critical > Fix For: 1.5.0 > > > We should add metrics to track events write to ElasticasearchSink. > eg. > * number of successful bulk sends > * number of documents inserted > * number of documents updated > * number of documents version conflicts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7947) Let ParameterTool return a dedicated GlobalJobParameters object
[
https://issues.apache.org/jira/browse/FLINK-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226117#comment-16226117
]
Hai Zhou UTC+8 commented on FLINK-7947:
---
+1
> Let ParameterTool return a dedicated GlobalJobParameters object
> ---
>
> Key: FLINK-7947
> URL: https://issues.apache.org/jira/browse/FLINK-7947
> Project: Flink
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.4.0
>Reporter: Till Rohrmann
>Assignee: Bowen Li
>
> The {{ParameterTool}} directly implements the {{GlobalJobParameters}}
> interface. Additionally it has grown over time to not only store the
> configuration parameters but also to record which parameters have been
> requested and what default value was set. This information is irrelevant on
> the server side when setting a {{GlobalJobParameters}} object via
> {{ExecutionConfig#setGlobalJobParameters}}.
> Since we don't separate the {{ParameterTool}} logic and the actual data view,
> users ran into problems when reusing the same {{ParameterTool}} to start
> multiple jobs concurrently (see FLINK-7943). I think it would be a much
> clearer separation of concerns if we would actually split the
> {{GlobalJobParameters}} from the {{ParameterTool}}.
> Furthermore, we should think about whether {{ParameterTool#get}} should have
> side effects or not as it does right now.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (FLINK-7893) Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reopened FLINK-7893: --- > Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint > --- > > Key: FLINK-7893 > URL: https://issues.apache.org/jira/browse/FLINK-7893 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsSubtasksHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7892) Port CheckpointStatsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7892. - Resolution: Fixed > Port CheckpointStatsHandler to new REST endpoint > > > Key: FLINK-7892 > URL: https://issues.apache.org/jira/browse/FLINK-7892 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7893) Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7893. - Resolution: Fixed > Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint > --- > > Key: FLINK-7893 > URL: https://issues.apache.org/jira/browse/FLINK-7893 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsSubtasksHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7885) Port CheckpointStatsDetailsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7885. - Resolution: Duplicate > Port CheckpointStatsDetailsHandler to new REST endpoint > --- > > Key: FLINK-7885 > URL: https://issues.apache.org/jira/browse/FLINK-7885 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (FLINK-7892) Port CheckpointStatsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reopened FLINK-7892: --- Assignee: (was: Hai Zhou UTC+8) > Port CheckpointStatsHandler to new REST endpoint > > > Key: FLINK-7892 > URL: https://issues.apache.org/jira/browse/FLINK-7892 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7884) Port CheckpointConfigHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7884. - Resolution: Duplicate > Port CheckpointConfigHandler to new REST endpoint > - > > Key: FLINK-7884 > URL: https://issues.apache.org/jira/browse/FLINK-7884 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointConfigHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (FLINK-7885) Port CheckpointStatsDetailsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reopened FLINK-7885: --- Assignee: (was: Hai Zhou UTC+8) > Port CheckpointStatsDetailsHandler to new REST endpoint > --- > > Key: FLINK-7885 > URL: https://issues.apache.org/jira/browse/FLINK-7885 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (FLINK-7884) Port CheckpointConfigHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reopened FLINK-7884: --- Assignee: (was: Hai Zhou UTC+8) > Port CheckpointConfigHandler to new REST endpoint > - > > Key: FLINK-7884 > URL: https://issues.apache.org/jira/browse/FLINK-7884 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointConfigHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7884) Port CheckpointConfigHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7884. - Resolution: Fixed > Port CheckpointConfigHandler to new REST endpoint > - > > Key: FLINK-7884 > URL: https://issues.apache.org/jira/browse/FLINK-7884 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointConfigHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7893) Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7893. - Resolution: Fixed > Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint > --- > > Key: FLINK-7893 > URL: https://issues.apache.org/jira/browse/FLINK-7893 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsSubtasksHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7885) Port CheckpointStatsDetailsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7885. - Resolution: Fixed > Port CheckpointStatsDetailsHandler to new REST endpoint > --- > > Key: FLINK-7885 > URL: https://issues.apache.org/jira/browse/FLINK-7885 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7892) Port CheckpointStatsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7892. - Resolution: Fixed > Port CheckpointStatsHandler to new REST endpoint > > > Key: FLINK-7892 > URL: https://issues.apache.org/jira/browse/FLINK-7892 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FLINK-7900) Add a Rich KeySelector
[ https://issues.apache.org/jira/browse/FLINK-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7900. - Resolution: Won't Fix > Add a Rich KeySelector > -- > > Key: FLINK-7900 > URL: https://issues.apache.org/jira/browse/FLINK-7900 > Project: Flink > Issue Type: Improvement > Components: DataStream API >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Critical > > Currently, we just have a `KeySelector` Function, maybe we should add a > `RichKeySelector` RichFunction, for the user to read some configuration > information to build the keySelector they need. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7900) Add a Rich KeySelector
[ https://issues.apache.org/jira/browse/FLINK-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7900: - Assignee: Hai Zhou UTC+8 > Add a Rich KeySelector > -- > > Key: FLINK-7900 > URL: https://issues.apache.org/jira/browse/FLINK-7900 > Project: Flink > Issue Type: Improvement > Components: DataStream API >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 >Priority: Critical > > Currently, we just have a `KeySelector` Function, maybe we should add a > `RichKeySelector` RichFunction, for the user to read some configuration > information to build the keySelector they need. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7900) Add a Rich KeySelector
Hai Zhou UTC+8 created FLINK-7900: - Summary: Add a Rich KeySelector Key: FLINK-7900 URL: https://issues.apache.org/jira/browse/FLINK-7900 Project: Flink Issue Type: Improvement Components: DataStream API Reporter: Hai Zhou UTC+8 Priority: Critical Currently, we just have a `KeySelector` Function, maybe we should add a `RichKeySelector` RichFunction, for the user to read some configuration information to build the keySelector they need. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7889) Enable dependency convergence for flink-streaming-java
[ https://issues.apache.org/jira/browse/FLINK-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7889: - Assignee: (was: Hai Zhou UTC+8) > Enable dependency convergence for flink-streaming-java > -- > > Key: FLINK-7889 > URL: https://issues.apache.org/jira/browse/FLINK-7889 > Project: Flink > Issue Type: Sub-task > Components: Build System >Affects Versions: 1.3.2 >Reporter: Piotr Nowojski > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7889) Enable dependency convergence for flink-streaming-java
[ https://issues.apache.org/jira/browse/FLINK-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7889: - Assignee: Hai Zhou UTC+8 > Enable dependency convergence for flink-streaming-java > -- > > Key: FLINK-7889 > URL: https://issues.apache.org/jira/browse/FLINK-7889 > Project: Flink > Issue Type: Sub-task > Components: Build System >Affects Versions: 1.3.2 >Reporter: Piotr Nowojski >Assignee: Hai Zhou UTC+8 > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7893) Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7893: -- Description: Port *CheckpointStatsDetailsSubtasksHandler* to new REST endpoint (was: Port *CheckpointStatsDetailsHandler* to new REST endpoint) > Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint > --- > > Key: FLINK-7893 > URL: https://issues.apache.org/jira/browse/FLINK-7893 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsSubtasksHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7893) Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7893: - Assignee: (was: Hai Zhou UTC+8) > Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint > --- > > Key: FLINK-7893 > URL: https://issues.apache.org/jira/browse/FLINK-7893 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7893) Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint
Hai Zhou UTC+8 created FLINK-7893: - Summary: Port CheckpointStatsDetailsSubtasksHandler to new REST endpoint Key: FLINK-7893 URL: https://issues.apache.org/jira/browse/FLINK-7893 Project: Flink Issue Type: Sub-task Components: Distributed Coordination, REST Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Fix For: 1.5.0 Port *CheckpointStatsDetailsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7892) Port CheckpointStatsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7892: -- Description: Port *CheckpointStatsHandler* to new REST endpoint (was: Port *CheckpointStatsDetailsHandler* to new REST endpoint) > Port CheckpointStatsHandler to new REST endpoint > > > Key: FLINK-7892 > URL: https://issues.apache.org/jira/browse/FLINK-7892 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7892) Port CheckpointStatsHandler to new REST endpoint
Hai Zhou UTC+8 created FLINK-7892: - Summary: Port CheckpointStatsHandler to new REST endpoint Key: FLINK-7892 URL: https://issues.apache.org/jira/browse/FLINK-7892 Project: Flink Issue Type: Sub-task Components: Distributed Coordination, REST Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Fix For: 1.5.0 Port *CheckpointStatsDetailsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7885) Port CheckpointStatsDetailsHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7885: -- Description: Port *CheckpointStatsDetailsHandler* to new REST endpoint (was: Port *ClusterConfigHandler* to new REST endpoint) Summary: Port CheckpointStatsDetailsHandler to new REST endpoint (was: Port ClusterConfigHandler to new REST endpoint) > Port CheckpointStatsDetailsHandler to new REST endpoint > --- > > Key: FLINK-7885 > URL: https://issues.apache.org/jira/browse/FLINK-7885 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointStatsDetailsHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7884) Port CheckpointConfigHandler to new REST endpoint
[ https://issues.apache.org/jira/browse/FLINK-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7884: -- Description: Port *CheckpointConfigHandler* to new REST endpoint (was: Port *ClusterOverviewHandler* to new REST endpoint) Summary: Port CheckpointConfigHandler to new REST endpoint (was: Port ClusterOverviewHandler to new REST endpoint) > Port CheckpointConfigHandler to new REST endpoint > - > > Key: FLINK-7884 > URL: https://issues.apache.org/jira/browse/FLINK-7884 > Project: Flink > Issue Type: Sub-task > Components: Distributed Coordination, REST >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.5.0 > > > Port *CheckpointConfigHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7885) Port ClusterConfigHandler to new REST endpoint
Hai Zhou UTC+8 created FLINK-7885: - Summary: Port ClusterConfigHandler to new REST endpoint Key: FLINK-7885 URL: https://issues.apache.org/jira/browse/FLINK-7885 Project: Flink Issue Type: Sub-task Components: Distributed Coordination, REST Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Fix For: 1.5.0 Port *ClusterConfigHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7884) Port ClusterOverviewHandler to new REST endpoint
Hai Zhou UTC+8 created FLINK-7884: - Summary: Port ClusterOverviewHandler to new REST endpoint Key: FLINK-7884 URL: https://issues.apache.org/jira/browse/FLINK-7884 Project: Flink Issue Type: Sub-task Components: Distributed Coordination, REST Reporter: Hai Zhou UTC+8 Assignee: Hai Zhou UTC+8 Fix For: 1.5.0 Port *ClusterOverviewHandler* to new REST endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FLINK-7879) only execute apache-rat in one build profile
[ https://issues.apache.org/jira/browse/FLINK-7879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 reassigned FLINK-7879: - Assignee: Hai Zhou UTC+8 > only execute apache-rat in one build profile > > > Key: FLINK-7879 > URL: https://issues.apache.org/jira/browse/FLINK-7879 > Project: Flink > Issue Type: Improvement > Components: Travis >Affects Versions: 1.4.0 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.4.0 > > > Similarly to [FLINK-7350|https://issues.apache.org/jira/browse/FLINK-7350] we > improve build times (and stability!) by only executing the Apache Rat plugin > in the build profile that builds the all of flink. > Bump apache-rat-plugin to 0.12, [RAT-173 > Cannot skip plugin run completely, but check only | > https://issues.apache.org/jira/browse/RAT-173] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7879) only execute apache-rat in one build profile
Hai Zhou UTC+8 created FLINK-7879: - Summary: only execute apache-rat in one build profile Key: FLINK-7879 URL: https://issues.apache.org/jira/browse/FLINK-7879 Project: Flink Issue Type: Improvement Components: Travis Affects Versions: 1.4.0 Reporter: Hai Zhou UTC+8 Fix For: 1.4.0 Similarly to [FLINK-7350|https://issues.apache.org/jira/browse/FLINK-7350] we improve build times (and stability!) by only executing the Apache Rat plugin in the build profile that builds the all of flink. Bump apache-rat-plugin to 0.12, [RAT-173 Cannot skip plugin run completely, but check only | https://issues.apache.org/jira/browse/RAT-173] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-6444) Add a check that '@VisibleForTesting' methods are only used in tests
[
https://issues.apache.org/jira/browse/FLINK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210831#comment-16210831
]
Hai Zhou UTC+8 commented on FLINK-6444:
---
Hi [~pnowojski], You could take a look at the above discussion. I wrote a
`flink-spotbugs-plugin` maven plugin with a detector to check this. although
it is very simple to use, but I do not know where to put it and how to deploy
to the public maven repository.
I'd like to hear your thoughts.
code commit:
https://github.com/yew1eb/flink/commit/d8edc6625ad98302cca54d80c5321d7fe3948b82
> Add a check that '@VisibleForTesting' methods are only used in tests
>
>
> Key: FLINK-6444
> URL: https://issues.apache.org/jira/browse/FLINK-6444
> Project: Flink
> Issue Type: Improvement
> Components: Build System
>Reporter: Stephan Ewen
>Assignee: mingleizhang
>
> Some methods are annotated with {{@VisibleForTesting}}. These methods should
> only be called from tests.
> This is currently not enforced / checked during the build. We should add such
> a check.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (FLINK-7819) Check object to clean is closure
[ https://issues.apache.org/jira/browse/FLINK-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 closed FLINK-7819. - Resolution: Won't Fix > Check object to clean is closure > > > Key: FLINK-7819 > URL: https://issues.apache.org/jira/browse/FLINK-7819 > Project: Flink > Issue Type: Bug > Components: Build System >Affects Versions: 1.3.2 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.4.0 > > > in *ClosureCleaner.clean(func) * method, we expect the *func* is closure. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLINK-7819) Check object to clean is closure
[ https://issues.apache.org/jira/browse/FLINK-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Zhou UTC+8 updated FLINK-7819: -- Description: in *ClosureCleaner.clean(func) * method, we expect the *func* is closure. (was: in *ClosureCleaner.clean(func) * method, we should check func is closure.) > Check object to clean is closure > > > Key: FLINK-7819 > URL: https://issues.apache.org/jira/browse/FLINK-7819 > Project: Flink > Issue Type: Bug > Components: Build System >Affects Versions: 1.3.2 >Reporter: Hai Zhou UTC+8 >Assignee: Hai Zhou UTC+8 > Fix For: 1.4.0 > > > in *ClosureCleaner.clean(func) * method, we expect the *func* is closure. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7777) Bump japicmp to 0.10.0
[
https://issues.apache.org/jira/browse/FLINK-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209045#comment-16209045
]
Hai Zhou UTC+8 commented on FLINK-:
---
True, I found more incompatible when switching to version 0.10.0...
{code:java}
[ERROR] Failed to execute goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.10.0:cmp (default) on project
flink-core: Breaking the build because there is at least one incompatibility:
org.apache.flink.core.fs.FileSystem.create(org.apache.flink.core.fs.Path,org.apache.flink.core.fs.FileSystem$WriteMode):METHOD_ABSTRACT_ADDED_TO_CLASS,org.apache.flink.core.fs.FileSystem$FSKey:CLASS_NOW_FINAL,org.apache.flink.core.fs.FileSystem$FSKey:CLASS_NO_LONGER_PUBLIC,org.apache.flink.core.fs.FSDataOutputStream.close():METHOD_ABSTRACT_ADDED_TO_CLASS,org.apache.flink.core.fs.FSDataOutputStream.getPos():METHOD_ABSTRACT_ADDED_TO_CLASS
-> [Help 1]
{code}
> Bump japicmp to 0.10.0
> --
>
> Key: FLINK-
> URL: https://issues.apache.org/jira/browse/FLINK-
> Project: Flink
> Issue Type: Bug
>Affects Versions: 1.3.2
>Reporter: Hai Zhou UTC+8
>Assignee: Hai Zhou UTC+8
>Priority: Minor
> Fix For: 1.5.0
>
>
> Currently, flink used japicmp-maven-plugin version is 0.7.0, I'm getting
> these warnings from the maven plugin during a *mvn clean verify*:
> {code:java}
> [INFO] Written file '.../target/japicmp/japicmp.diff'.
> [INFO] Written file '.../target/japicmp/japicmp.xml'.
> [INFO] Written file '.../target/japicmp/japicmp.html'.
> Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> Compiler warnings:
> WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property
> 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
> Warning: org.apache.xerces.parsers.SAXParser: Feature
> 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Property
> 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> {code}
> japicmp fixed in version 0.7.1 : _Excluded xerces vom maven-reporting
> dependency in order to prevent warnings from SAXParserImpl. _
> The current stable version is 0.10.0, we can consider upgrading to this
> version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
