Chesnay Schepler created FLINK-3308:
---
Summary: [py] Remove debug mode
Key: FLINK-3308
URL: https://issues.apache.org/jira/browse/FLINK-3308
Project: Flink
Issue Type: Improvement
Dear Flink-Devs,
I recently ran into a problem where range-partitioning within iterations
would be useful.
In the PR for range-partitioning it is said, this doesn't work because
of some batched data-exchange mode.
https://github.com/apache/flink/pull/1255
I would like to understand the issu
Chesnay Schepler created FLINK-3309:
---
Summary: [py] Resolve maven warnings
Key: FLINK-3309
URL: https://issues.apache.org/jira/browse/FLINK-3309
Project: Flink
Issue Type: Improvement
Hi Fridtjof,
the range partitioner works by building a histogram for the partitioning
key. This requires a pass over the whole intermediate data set which means
it needs to be materialized and cannot be processed in a pipelined fashion.
However, pipelined data exchange strategies are a requirement
Hi Fabian,
thanks for your explanation!
Yeah, I figured that if an easy fix exists, you would have done that yourself.
This is more for me to understand the conceptual problem.
But back to the pipeline-requirement: Doesn't zipWithIndex violate that too,
then? It's also a mapPartitions, collec
Hi,
I get the following exception when I execute a code similar to the
ALSITSuite. I train a ALS model and when the following code is executed
I get the error:
val predictions = als
.predict(testData)
.collect()
Exception in thread "main"
org.apache.flink.runtime.client.Job
Hi Hilmi,
could you check what happened on the JobManager side?
Cheers,
Till
On Mon, Feb 1, 2016 at 2:39 PM, Hilmi Yildirim
wrote:
> Hi,
>
> I get the following exception when I execute a code similar to the
> ALSITSuite. I train a ALS model and when the following code is executed I
> get t
Hi,
I started the code with ExecutionEnvironment.createLocalEnvironment()
Are there logs of the jobmanager in local mode?
Best Regards,
Hilmi
Am 01.02.2016 um 14:50 schrieb Till Rohrmann:
Hi Hilmi,
could you check what happened on the JobManager side?
Cheers,
Till
On Mon, Feb 1, 2016 at
Yes if you provide a log4j.properties file in your class path which sets
the log level to INFO and adds a console logger, you should see the output
in the IntelliJ console.
E.g.
log4j.rootLogger=INFO, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=or
It seems that the exception is caused by a OutOfMemoryError. But this is
only visible in the logs
Am 01.02.2016 um 15:17 schrieb Till Rohrmann:
Yes if you provide a log4j.properties file in your class path which sets
the log level to INFO and adds a console logger, you should see the output
in
> On 01 Feb 2016, at 16:45, Hilmi Yildirim wrote:
>
> It seems that the exception is caused by a OutOfMemoryError. But this is only
> visible in the logs
Could you share the relevant parts?
– Ufuk
Hey all,
Our release-0.10 branch contains some important fixes (for example a
critical fix in the network stack). I would like to hear your opinions
about doing a 0.10.2 bug fix release.
I think it's a good idea to go for it now. Even though we have the 1.0.0
release coming up, it's not clear whe
Ufuk Celebi created FLINK-3310:
--
Summary: Add back pressure statistics to web frontend
Key: FLINK-3310
URL: https://issues.apache.org/jira/browse/FLINK-3310
Project: Flink
Issue Type: Improvemen
Robert Metzger created FLINK-3311:
-
Summary: Add a connector for streaming data into Cassandra
Key: FLINK-3311
URL: https://issues.apache.org/jira/browse/FLINK-3311
Project: Flink
Issue Type:
+1 for a 0.10.2 maintenance release.
On Monday, February 1, 2016, Ufuk Celebi wrote:
> Hey all,
>
> Our release-0.10 branch contains some important fixes (for example a
> critical fix in the network stack). I would like to hear your opinions
> about doing a 0.10.2 bug fix release.
>
> I think it
Stephan Ewen created FLINK-3312:
---
Summary: Add convenience accessor methods for extended state
interface
Key: FLINK-3312
URL: https://issues.apache.org/jira/browse/FLINK-3312
Project: Flink
Is
16 matches
Mail list logo