[jira] [Created] (FLINK-7123) Support timesOrMore in CEP

Dian Fu created FLINK-7123: -- Summary: Support timesOrMore in CEP Key: FLINK-7123 URL: https://issues.apache.org/jira/browse/FLINK-7123 Project: Flink Issue Type: Sub-task Components: CEP

Re: Make SubmittedJobGraphStore configurable

Sure, ​ I would imagine ​couple of extra lines within flink.conf ​...​ graphstore.type: customized/zookeeper graphstore.class: ​org​ . ​apache.flink.contrib​ .MyS3SubmittedJobGraphStoreImp graphstore.endpoint: s3.amazonaws.com graphstore.path.root: s3://my root/ which overwrites initiation of *or

Re: How to set jobmanager.rpc.address in TaskManger node in HA cluster

Sorry. I didn't put high-availability: zookeeper in taskmangers' flink-config.yml. After I fixed this, everything went well. On Fri, Jul 7, 2017 at 11:08 AM, Mu Kong wrote: > Hi all, > > I'm trying setup an HA Flink cluster with 3 job managers and 3 task > managers. > After executing start-clust

[jira] [Created] (FLINK-7122) When metric name contains special characters then Graphite will not display them

wyp created FLINK-7122: -- Summary: When metric name contains special characters then Graphite will not display them Key: FLINK-7122 URL: https://issues.apache.org/jira/browse/FLINK-7122 Project: Flink I

[jira] [Created] (FLINK-7121) Remove the hardcoded way in core

mingleizhang created FLINK-7121: --- Summary: Remove the hardcoded way in core Key: FLINK-7121 URL: https://issues.apache.org/jira/browse/FLINK-7121 Project: Flink Issue Type: Bug Compon

How to set jobmanager.rpc.address in TaskManger node in HA cluster

Hi all, I'm trying setup an HA Flink cluster with 3 job managers and 3 task managers. After executing start-cluster.sh, 3 job managers are normally started. However, the task managers are still down due to an exception showed below: org.apache.flink.util.ConfigurationException: Config parameter '

[jira] [Created] (FLINK-7120) Remove the hardcoded way in Utils

mingleizhang created FLINK-7120: --- Summary: Remove the hardcoded way in Utils Key: FLINK-7120 URL: https://issues.apache.org/jira/browse/FLINK-7120 Project: Flink Issue Type: Bug Compo

[jira] [Created] (FLINK-7119) Remove the hardcoded way in HadoopUtils

mingleizhang created FLINK-7119: --- Summary: Remove the hardcoded way in HadoopUtils Key: FLINK-7119 URL: https://issues.apache.org/jira/browse/FLINK-7119 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-7118) Remove hadoop1.x code in HadoopUtils

mingleizhang created FLINK-7118: --- Summary: Remove hadoop1.x code in HadoopUtils Key: FLINK-7118 URL: https://issues.apache.org/jira/browse/FLINK-7118 Project: Flink Issue Type: Bug Co

[jira] [Created] (FLINK-7117) Add JobManagerLeaderRetrieval method with default JobManager address

Till Rohrmann created FLINK-7117: Summary: Add JobManagerLeaderRetrieval method with default JobManager address Key: FLINK-7117 URL: https://issues.apache.org/jira/browse/FLINK-7117 Project: Flink

[jira] [Created] (FLINK-7116) Add getPort method to RpcService

Till Rohrmann created FLINK-7116: Summary: Add getPort method to RpcService Key: FLINK-7116 URL: https://issues.apache.org/jira/browse/FLINK-7116 Project: Flink Issue Type: Sub-task

Re: [DISCUSS] FLIP proposal for Model Serving over Flink

Thanx Fabian! I asked Robert for that already, but I will let you know then :) Best, Stavros On Thu, Jul 6, 2017 at 10:10 PM, Fabian Hueske wrote: > Great, thank you Theodore! > > @Stavros Let me know when you need edit permissions to add the FLIP to the > wiki. > > Cheers, > Fabian > > 2017-07

Re: Tips to fix IDEA strange problem after updating master code

I’m wondering if we can remove the ILoopCompat duplication by checking and reading the trait properties with reflection … but I have not discovered how to do this. > On Jul 4, 2017, at 3:57 AM, Piotr Nowojski wrote: > > Besides deactivating “scala-2.10” profile in the Intellij it might be >

Re: [DISCUSS] FLIP proposal for Model Serving over Flink

Great, thank you Theodore! @Stavros Let me know when you need edit permissions to add the FLIP to the wiki. Cheers, Fabian 2017-07-06 2:33 GMT+02:00 Theodore Vasiloudis < theodoros.vasilou...@gmail.com>: > Hello all, > > I just wanted to indicate that I would be very willing to help out with >

[jira] [Created] (FLINK-7115) test instability in MiniClusterITCase.runJobWithMultipleJobManagers

-Amz-Date=20170706T151556Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170706/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=5b7c512137c7cbd82dcb77a98aeadc3d761b7055bea6d8f07ad

[jira] [Created] (FLINK-7114) Remove the hardcoded way in flink

mingleizhang created FLINK-7114: --- Summary: Remove the hardcoded way in flink Key: FLINK-7114 URL: https://issues.apache.org/jira/browse/FLINK-7114 Project: Flink Issue Type: Bug Rep

Re:[DISCUSS]refactor StreamConfig

Hi Aljoscha: Great. I cannot agree with you more. So I introduce OperatorSettings and OperatorProperties. StreamTaskConfig relys on the underlying configuration and is provided for the streamTask to use. It contains: 1) in.physical.edges 2) out.physical.edges 3) chained

Re: Tips to fix IDEA strange problem after updating master code

First of all by activating scala-2.10/2.11 profile we change two properties to some predefined values: 2.10.6 2.10 To drop profile for that, one would have to overwrite both of those properties simultaneously. Secondly yes, we h

Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

@Ted Good idea. Using the “Release Note” field would definitely be better than some dangling comment. On 6 July 2017 at 6:35:24 PM, Ted Yu (yuzhih...@gmail.com) wrote: Thru INFRA-14519, Release Note field has been added to JIRA.  We can use this field to record API/ compatibility changes. 

Re: Re: Tips to fix IDEA strange problem after updating master code

Is it possible to not use a profile for that, but only an actual property variable? Or do we use different dependencies with Scala 2.10 vs Scala 2.11 ? On Tue, Jul 4, 2017 at 11:23 AM, 郭健 wrote: > After deactivating scala-2.10 profile in IntelliJ, this issue is gone. > Thank you all. > > On 7/4

[jira] [Created] (FLINK-7113) Make ClusterDescriptor independent of Flink cluster size

Till Rohrmann created FLINK-7113: Summary: Make ClusterDescriptor independent of Flink cluster size Key: FLINK-7113 URL: https://issues.apache.org/jira/browse/FLINK-7113 Project: Flink Issue

Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

Thru INFRA-14519, Release Note field has been added to JIRA.  We can use this field to record API/ compatibility changes.  Original message From: Aljoscha Krettek Date: 7/6/17 2:01 AM (GMT-08:00) To: dev@flink.apache.org Subject: Re: [DISCUSS] Managing announcements of breakin

Re: Make SubmittedJobGraphStore configurable

The sample config entries are broken into multiple lines. Can you send the config again with one config on one line ? Cheers On Wed, Jul 5, 2017 at 10:19 PM, Chen Qin wrote: > ​Hi there, > > ​I would like to propose/discuss median level refactor work to make > submittedJobGraphStore configurab

[jira] [Created] (FLINK-7112) YARNSessionCapacitySchedulerITCase uses example jar without dependency

Chesnay Schepler created FLINK-7112: --- Summary: YARNSessionCapacitySchedulerITCase uses example jar without dependency Key: FLINK-7112 URL: https://issues.apache.org/jira/browse/FLINK-7112 Project: F

Re: refactor StreamConfig

Hi, Yes, the fact that the operator can see isChainStart() and isChainEnd() is not good, in my opinion. These seems to be an implementation detail that an operator should not be aware of. For now it’s ok but maybe we can fix that later. Regarding output edges and serialisers, I think it might

Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

+1 This sounds very good! I just hope that everyone is aware enough and doesn’t forget adding these tags. > On 6. Jul 2017, at 09:59, Tzu-Li (Gordon) Tai wrote: > > > Hi devs, > > I would like to follow up my proposal in [1] regarding how we can more > systematically and easily collect brea

[jira] [Created] (FLINK-7111) flink-scala-shell fails on mvn verify

Chesnay Schepler created FLINK-7111: --- Summary: flink-scala-shell fails on mvn verify Key: FLINK-7111 URL: https://issues.apache.org/jira/browse/FLINK-7111 Project: Flink Issue Type: Bug

Re: [DISCUSS] Release 1.3.2 planning

I’m seeing these remaining blockers: https://issues.apache.org/jira/browse/FLINK-7069?filter=12334772&jql=project%20%3D%20FLINK%20AND%20priority%20%3D%20Blocker%20AND%20resolution%20%3D%20Unresolved

[DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

Hi devs, I would like to follow up my proposal in [1] regarding how we can more systematically and easily collect breaking changes, so that major release announcements can officially include a list of such changes. Originally the idea was to collect these in the Wiki whenever a breaking change

[jira] [Created] (FLINK-7110) Add deploy with job to ClusterDescriptor

Till Rohrmann created FLINK-7110: Summary: Add deploy with job to ClusterDescriptor Key: FLINK-7110 URL: https://issues.apache.org/jira/browse/FLINK-7110 Project: Flink Issue Type: Sub-task