Re: improper use of releaseJob() without a matching number of createTmpFiles() calls for jobId

2019-01-22 Thread Chang Liu
Hi Stefan, I have upgraded to 1.6.1. I saw the warnings are gone but my issue remains: the scenarios: Set[Scenario] cannot be passed as a method argument in order to be used in the map function. But it is working if I just directly use the object variable scenarios: Set[Scenario] instead of

Re: improper use of releaseJob() without a matching number of createTmpFiles() calls for jobId

2019-01-22 Thread Chang Liu
Hi Stefan, Thanks. I am using 1.6.0. I will upgrade to 1.6.1 and see whether the problem remains. Best regards/祝好, Chang Liu 刘畅 > On 22 Jan 2019, at 16:10, Stefan Richter wrote: > > Hi, > > Which version of Flink are you using? This issue >

Re: improper use of releaseJob() without a matching number of createTmpFiles() calls for jobId

2019-01-22 Thread Stefan Richter
Hi, Which version of Flink are you using? This issue https://issues.apache.org/jira/browse/FLINK-10283 shows that a similar problem was fixed in 1.6.1 and 1.7. If you use a newer version and still encounter the problem, you can reopen the

Re: improper use of releaseJob() without a matching number of createTmpFiles() calls for jobId

2019-01-22 Thread Chang Liu
I have tried another way, it is not working as well: def evaluationStream( indicatorsStream: DataStream[Indicators], scenarios: Set[Scenario]): DataStream[Evaluation] = indicatorsStream.map(new IndicatorsToTxEval(scenarios)) class IndicatorsToTxEval( scenarios: Set[Scenario])

Re: improper use of releaseJob() without a matching number of createTmpFiles() calls for jobId

2019-01-22 Thread Chang Liu
Ok, I think I found where is the issue, but I don’t understand why. I have a method: def evaluationStream( indicatorsStream: DataStream[Indicators], scenarios: Set[Scenario]): DataStream[Evaluation] = indicatorsStream.map { indicators => Evaluation(indicators.id

improper use of releaseJob() without a matching number of createTmpFiles() calls for jobId

2019-01-22 Thread Chang Liu
Dear community, I am having a problem releasing the job. 2019-01-22 10:42:50.098 WARN [Source: Custom Source -> Kafka -> ConstructTxSepa -> FilterOutFailures -> ObtainActualTxSepa -> TxSepaStream -> TxStream -> IndicatorsEvalStream -> TxEvalStream -> Sink: Print to Std. Out (2/4)]