[jira] [Created] (FLINK-10467) Upgrade commons-compress to 1.18
Ted Yu created FLINK-10467: -- Summary: Upgrade commons-compress to 1.18 Key: FLINK-10467 URL: https://issues.apache.org/jira/browse/FLINK-10467 Project: Flink Issue Type: Task Reporter: Ted Yu org.apache.commons:commons-compress defines an API for working with compression and archive formats. Affected versions of this package are vulnerable to Directory Traversal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-10466) flink-yarn-tests should depend flink-dist
tison created FLINK-10466:
-
Summary: flink-yarn-tests should depend flink-dist
Key: FLINK-10466
URL: https://issues.apache.org/jira/browse/FLINK-10466
Project: Flink
Issue Type: Bug
Components: Tests
Affects Versions: 1.7.0
Reporter: tison
Assignee: Chesnay Schepler
Fix For: 1.7.0
may be adding
{code:java}
org.apache.flink
flink-dist_${scala.binary.version}
${project.version}
test
pom
{code}
not really sure but it causes failure on my automate testing process, and by
adding this dependency the error disappear. Even I wonder how it works
currently on travis.
flink-yarn-test obviously depends on flink-dist since some tests try to find
flink uberjar.
Please take a look for this. cc [~Zentol]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FLINK-10465) Jepsen: runit supervised sshd is stopped on tear down
Gary Yao created FLINK-10465:
Summary: Jepsen: runit supervised sshd is stopped on tear down
Key: FLINK-10465
URL: https://issues.apache.org/jira/browse/FLINK-10465
Project: Flink
Issue Type: Bug
Components: Tests
Affects Versions: 1.7.0, 1.6.2
Reporter: Gary Yao
Assignee: Gary Yao
Fix For: 1.7.0, 1.6.2
When tearing down the _DB_, we tear down all services supervised by runit.
However when running the tests in Docker, sshd is under supervision by runit.
When sshd is stopped, the tests cannot be continued because the control node
cannot interact with the DB nodes anymore.
*How to reproduce*
Run command below in control-node container:
{code}
./docker/run-tests.sh 1
[...]/flink/flink-1.6.1/flink-1.6.1-bin-hadoop28-scala_2.11.tgz
{code}
*Expected behavior*
sshd should never be stopped
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FLINK-10464) TimeIndicatorRelDataType: digest can not describe a type completely.
huangjiatian created FLINK-10464: Summary: TimeIndicatorRelDataType: digest can not describe a type completely. Key: FLINK-10464 URL: https://issues.apache.org/jira/browse/FLINK-10464 Project: Flink Issue Type: Bug Reporter: huangjiatian I met a strange question when i use Flink SQL API. The error message like that: java.lang.AssertionError: Conversion to relational algebra failed to preserve datatypes: validated type: RecordType(TIMESTAMP(3) NOT NULL rowtime) NOT NULL converted type: RecordType(TIMESTAMP(3) NOT NULL rowtime) NOT NULL rel: LogicalProject(rowtime=[$3]) LogicalTableScan(table=[[hjtsrc]]) I found two difference type are considered equal. !image-2018-09-28-13-11-43-515.png! that mean, "select deviceid, rowtime.rowtime" equal to "select deviceid, rowtime.proctime" "digest" in TimeIndicatorRelDataType without event time message , it can not describe a TimeIndicatorRelDataType completely. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] Dropping flink-storm?
I would drop it. Niels Basjes On Sat, 29 Sep 2018, 10:38 Kostas Kloudas, wrote: > +1 to drop it as nobody seems to be willing to maintain it and it also > stands in the way for future developments in Flink. > > Cheers, > Kostas > > > On Sep 29, 2018, at 8:19 AM, Tzu-Li Chen wrote: > > > > +1 to drop it. > > > > It seems few people use it. Commits history of an experimental > > module sparse often means that there is low interest. > > > > Best, > > tison. > > > > > > 远远 于2018年9月29日周六 下午2:16写道： > > > >> +1， it‘s time to drop it > >> > >> Zhijiang(wangzhijiang999) 于2018年9月29日周六 > >> 下午1:53写道： > >> > >>> Very agree with to drop it. +1 > >>> > >>> -- > >>> 发件人：Jeff Carter > >>> 发送时间：2018年9月29日(星期六) 10:18 > >>> 收件人：dev > >>> 抄 送：chesnay ; Till Rohrmann >; > >>> user > >>> 主 题：Re: [DISCUSS] Dropping flink-storm? > >>> > >>> +1 to drop it. > >>> > >>> On Fri, Sep 28, 2018, 7:25 PM Hequn Cheng > wrote: > >>> > Hi, > > +1 to drop it. It seems that few people use it. > > Best, Hequn > > On Fri, Sep 28, 2018 at 10:22 PM Chesnay Schepler > > wrote: > > > I'm very much in favor of dropping it. > > > > Flink has been continually growing in terms of features, and IMO > we've > > reached the point where we should cull some of the more obscure ones. > >>> > > flink-storm, while interesting from a theoretical standpoint, offers > too > > little value. > > > >>> > > Note that the bolt/spout wrapper parts of the part are still > compatible, > > it's only topologies that aren't working. > > > > IMO compatibility layers only add value if they ease the migration to > > Flink APIs. > >>> > > * bolt/spout wrappers do this, but they will continue to work even > if we > > drop it > > * topologies don't do this, so I'm not interested in then. > > > > On 28.09.2018 15:22, Till Rohrmann wrote: > >> Hi everyone, > >> > >> I would like to discuss how to proceed with Flink's storm > >> compatibility layer flink-strom. > >> > >> While working on removing Flink's legacy mode, I noticed that some > >>> > >> parts of flink-storm rely on the legacy Flink client. In fact, at > the > >>> > >> moment flink-storm does not work together with Flink's new > distributed > >> architecture. > >> > >> I'm also wondering how many people are actually using Flink's Storm > >> compatibility layer and whether it would be worth porting it. > >> > >> I see two options how to proceed: > >> > >> 1) Commit to maintain flink-storm and port it to Flink's new > architecture > >> 2) Drop flink-storm > >> > >>> > >> I doubt that we can contribute it to Apache Bahir [1], because once > we > >>> > >> remove the legacy mode, this module will no longer work with all > newer > >> Flink versions. > >> > >>> > >> Therefore, I would like to hear your opinion on this and in > particular > >> if you are using or planning to use flink-storm in the future. > >> > >> [1] https://github.com/apache/bahir-flink > >> > >> Cheers, > >> Till > > > > > > > > >>> > >>> > >>> > >
Re: [DISCUSS] Dropping flink-storm?
+1 to drop it as nobody seems to be willing to maintain it and it also stands in the way for future developments in Flink. Cheers, Kostas > On Sep 29, 2018, at 8:19 AM, Tzu-Li Chen wrote: > > +1 to drop it. > > It seems few people use it. Commits history of an experimental > module sparse often means that there is low interest. > > Best, > tison. > > > 远远 于2018年9月29日周六 下午2:16写道： > >> +1， it‘s time to drop it >> >> Zhijiang(wangzhijiang999) 于2018年9月29日周六 >> 下午1:53写道： >> >>> Very agree with to drop it. +1 >>> >>> -- >>> 发件人：Jeff Carter >>> 发送时间：2018年9月29日(星期六) 10:18 >>> 收件人：dev >>> 抄 送：chesnay ; Till Rohrmann ; >>> user >>> 主 题：Re: [DISCUSS] Dropping flink-storm? >>> >>> +1 to drop it. >>> >>> On Fri, Sep 28, 2018, 7:25 PM Hequn Cheng wrote: >>> Hi, +1 to drop it. It seems that few people use it. Best, Hequn On Fri, Sep 28, 2018 at 10:22 PM Chesnay Schepler wrote: > I'm very much in favor of dropping it. > > Flink has been continually growing in terms of features, and IMO we've > reached the point where we should cull some of the more obscure ones. >>> > flink-storm, while interesting from a theoretical standpoint, offers too > little value. > >>> > Note that the bolt/spout wrapper parts of the part are still compatible, > it's only topologies that aren't working. > > IMO compatibility layers only add value if they ease the migration to > Flink APIs. >>> > * bolt/spout wrappers do this, but they will continue to work even if we > drop it > * topologies don't do this, so I'm not interested in then. > > On 28.09.2018 15:22, Till Rohrmann wrote: >> Hi everyone, >> >> I would like to discuss how to proceed with Flink's storm >> compatibility layer flink-strom. >> >> While working on removing Flink's legacy mode, I noticed that some >>> >> parts of flink-storm rely on the legacy Flink client. In fact, at the >>> >> moment flink-storm does not work together with Flink's new distributed >> architecture. >> >> I'm also wondering how many people are actually using Flink's Storm >> compatibility layer and whether it would be worth porting it. >> >> I see two options how to proceed: >> >> 1) Commit to maintain flink-storm and port it to Flink's new architecture >> 2) Drop flink-storm >> >>> >> I doubt that we can contribute it to Apache Bahir [1], because once we >>> >> remove the legacy mode, this module will no longer work with all newer >> Flink versions. >> >>> >> Therefore, I would like to hear your opinion on this and in particular >> if you are using or planning to use flink-storm in the future. >> >> [1] https://github.com/apache/bahir-flink >> >> Cheers, >> Till > > > >>> >>> >>>
[jira] [Created] (FLINK-10463) Null literal cannot be properly parsed in Java Table API function call
Xingcan Cui created FLINK-10463:
---
Summary: Null literal cannot be properly parsed in Java Table API
function call
Key: FLINK-10463
URL: https://issues.apache.org/jira/browse/FLINK-10463
Project: Flink
Issue Type: Bug
Components: Table API SQL
Reporter: Xingcan Cui
For example, the expression `Null(STRING).regexpReplace('oo|ar', '')` throws
the following exception.
{code:java}
org.apache.flink.table.api.ExpressionParserException: Could not parse
expression at column 13: string matching regex
`(?i)\Qas\E(?![_$\p{javaJavaIdentifierPart}])' expected but `.' found
Null(STRING).regexpReplace('oo|ar', '')
^
at
org.apache.flink.table.expressions.ExpressionParser$.throwError(ExpressionParser.scala:576)
at
org.apache.flink.table.expressions.ExpressionParser$.parseExpression(ExpressionParser.scala:569)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [DISCUSS] Dropping flink-storm?
+1 to drop it. It seems few people use it. Commits history of an experimental module sparse often means that there is low interest. Best, tison. 远远 于2018年9月29日周六 下午2:16写道： > +1， it‘s time to drop it > > Zhijiang(wangzhijiang999) 于2018年9月29日周六 > 下午1:53写道： > >> Very agree with to drop it. +1 >> >> -- >> 发件人：Jeff Carter >> 发送时间：2018年9月29日(星期六) 10:18 >> 收件人：dev >> 抄 送：chesnay ; Till Rohrmann ; >> user >> 主 题：Re: [DISCUSS] Dropping flink-storm? >> >> +1 to drop it. >> >> On Fri, Sep 28, 2018, 7:25 PM Hequn Cheng wrote: >> >> > Hi, >> > >> > +1 to drop it. It seems that few people use it. >> > >> > Best, Hequn >> > >> > On Fri, Sep 28, 2018 at 10:22 PM Chesnay Schepler >> > wrote: >> > >> > > I'm very much in favor of dropping it. >> > > >> > > Flink has been continually growing in terms of features, and IMO we've >> > > reached the point where we should cull some of the more obscure ones. >> >> > > flink-storm, while interesting from a theoretical standpoint, offers too >> > > little value. >> > > >> >> > > Note that the bolt/spout wrapper parts of the part are still compatible, >> > > it's only topologies that aren't working. >> > > >> > > IMO compatibility layers only add value if they ease the migration to >> > > Flink APIs. >> >> > > * bolt/spout wrappers do this, but they will continue to work even if we >> > > drop it >> > > * topologies don't do this, so I'm not interested in then. >> > > >> > > On 28.09.2018 15:22, Till Rohrmann wrote: >> > > > Hi everyone, >> > > > >> > > > I would like to discuss how to proceed with Flink's storm >> > > > compatibility layer flink-strom. >> > > > >> > > > While working on removing Flink's legacy mode, I noticed that some >> >> > > > parts of flink-storm rely on the legacy Flink client. In fact, at the >> >> > > > moment flink-storm does not work together with Flink's new distributed >> > > > architecture. >> > > > >> > > > I'm also wondering how many people are actually using Flink's Storm >> > > > compatibility layer and whether it would be worth porting it. >> > > > >> > > > I see two options how to proceed: >> > > > >> > > > 1) Commit to maintain flink-storm and port it to Flink's new >> > architecture >> > > > 2) Drop flink-storm >> > > > >> >> > > > I doubt that we can contribute it to Apache Bahir [1], because once we >> >> > > > remove the legacy mode, this module will no longer work with all newer >> > > > Flink versions. >> > > > >> >> > > > Therefore, I would like to hear your opinion on this and in particular >> > > > if you are using or planning to use flink-storm in the future. >> > > > >> > > > [1] https://github.com/apache/bahir-flink >> > > > >> > > > Cheers, >> > > > Till >> > > >> > > >> > > >> > >> >> >>
Re: [DISCUSS] Dropping flink-storm?
+1， it‘s time to drop it Zhijiang(wangzhijiang999) 于2018年9月29日周六 下午1:53写道： > Very agree with to drop it. +1 > > -- > 发件人：Jeff Carter > 发送时间：2018年9月29日(星期六) 10:18 > 收件人：dev > 抄 送：chesnay ; Till Rohrmann ; > user > 主 题：Re: [DISCUSS] Dropping flink-storm? > > +1 to drop it. > > On Fri, Sep 28, 2018, 7:25 PM Hequn Cheng wrote: > > > Hi, > > > > +1 to drop it. It seems that few people use it. > > > > Best, Hequn > > > > On Fri, Sep 28, 2018 at 10:22 PM Chesnay Schepler > > wrote: > > > > > I'm very much in favor of dropping it. > > > > > > Flink has been continually growing in terms of features, and IMO we've > > > reached the point where we should cull some of the more obscure ones. > > > > flink-storm, while interesting from a theoretical standpoint, offers too > > > little value. > > > > > > > Note that the bolt/spout wrapper parts of the part are still compatible, > > > it's only topologies that aren't working. > > > > > > IMO compatibility layers only add value if they ease the migration to > > > Flink APIs. > > > > * bolt/spout wrappers do this, but they will continue to work even if we > > > drop it > > > * topologies don't do this, so I'm not interested in then. > > > > > > On 28.09.2018 15:22, Till Rohrmann wrote: > > > > Hi everyone, > > > > > > > > I would like to discuss how to proceed with Flink's storm > > > > compatibility layer flink-strom. > > > > > > > > While working on removing Flink's legacy mode, I noticed that some > > > > parts of flink-storm rely on the legacy Flink client. In fact, at the > > > > > moment flink-storm does not work together with Flink's new distributed > > > > architecture. > > > > > > > > I'm also wondering how many people are actually using Flink's Storm > > > > compatibility layer and whether it would be worth porting it. > > > > > > > > I see two options how to proceed: > > > > > > > > 1) Commit to maintain flink-storm and port it to Flink's new > > architecture > > > > 2) Drop flink-storm > > > > > > > > > I doubt that we can contribute it to Apache Bahir [1], because once we > > > > > remove the legacy mode, this module will no longer work with all newer > > > > Flink versions. > > > > > > > > > Therefore, I would like to hear your opinion on this and in particular > > > > if you are using or planning to use flink-storm in the future. > > > > > > > > [1] https://github.com/apache/bahir-flink > > > > > > > > Cheers, > > > > Till > > > > > > > > > > > > > >
