Till Rohrmann created FLINK-7093:
Summary: Send SlotReport as part of the heartbeat payload to the RM
Key: FLINK-7093
URL: https://issues.apache.org/jira/browse/FLINK-7093
Project: Flink
Issu
Till Rohrmann created FLINK-7092:
Summary: Shutdown ResourceManager components properly
Key: FLINK-7092
URL: https://issues.apache.org/jira/browse/FLINK-7092
Project: Flink
Issue Type: Sub-ta
Till Rohrmann created FLINK-7091:
Summary: Rework ReconciliationCoordinator to not depend on Akka
Key: FLINK-7091
URL: https://issues.apache.org/jira/browse/FLINK-7091
Project: Flink
Issue Ty
Till Rohrmann created FLINK-7090:
Summary: Rework ConnectionMonitor to not depend on Akka
Key: FLINK-7090
URL: https://issues.apache.org/jira/browse/FLINK-7090
Project: Flink
Issue Type: Sub-
Till Rohrmann created FLINK-7089:
Summary: Rework LaunchCoordinator to not depend on Akka
Key: FLINK-7089
URL: https://issues.apache.org/jira/browse/FLINK-7089
Project: Flink
Issue Type: Sub-
Till Rohrmann created FLINK-7088:
Summary: Rework TaskMonitor to not depend on Akka
Key: FLINK-7088
URL: https://issues.apache.org/jira/browse/FLINK-7088
Project: Flink
Issue Type: Sub-task
Till Rohrmann created FLINK-7087:
Summary: Implement Flip-6 container entry point
Key: FLINK-7087
URL: https://issues.apache.org/jira/browse/FLINK-7087
Project: Flink
Issue Type: Bug
Till Rohrmann created FLINK-7086:
Summary: Create entry point for standalone session mode
Key: FLINK-7086
URL: https://issues.apache.org/jira/browse/FLINK-7086
Project: Flink
Issue Type: Sub-
Till Rohrmann created FLINK-7085:
Summary: Test slot allocation protocol
Key: FLINK-7085
URL: https://issues.apache.org/jira/browse/FLINK-7085
Project: Flink
Issue Type: Sub-task
Co
Till Rohrmann created FLINK-7084:
Summary: Flip-6 testing
Key: FLINK-7084
URL: https://issues.apache.org/jira/browse/FLINK-7084
Project: Flink
Issue Type: Test
Components: Tests
Looks like the picture didn't go thru.
Mind using third party site ?
Thanks
On Mon, Jul 3, 2017 at 8:56 PM, Jark Wu wrote:
> Hi devs,
>
> Yesterday, I updated the master code which include [FLINK-7030]: Build
> with scala-2.11 by default. After that, I entered a strange problem with
> IDEA tha
Hi devs,
Yesterday, I updated the master code which include [FLINK-7030]: Build with
scala-2.11 by default. After that, I entered a strange problem with IDEA
that many classes can't be found, and the project can't be built/compiled
(in IDEA), but maven install worked good.
After a series of attem
Till Rohrmann created FLINK-7083:
Summary: Adapt WebRuntimeMonitor to work with Flip-6 architecture
Key: FLINK-7083
URL: https://issues.apache.org/jira/browse/FLINK-7083
Project: Flink
Issue
Till Rohrmann created FLINK-7082:
Summary: Flip-6: Generic entry point for Flink sessions
Key: FLINK-7082
URL: https://issues.apache.org/jira/browse/FLINK-7082
Project: Flink
Issue Type: Bug
Till Rohrmann created FLINK-7081:
Summary: Deploy Mesos framework with job
Key: FLINK-7081
URL: https://issues.apache.org/jira/browse/FLINK-7081
Project: Flink
Issue Type: Sub-task
Till Rohrmann created FLINK-7080:
Summary: Deploy Yarn cluster with job
Key: FLINK-7080
URL: https://issues.apache.org/jira/browse/FLINK-7080
Project: Flink
Issue Type: Sub-task
Com
Till Rohrmann created FLINK-7079:
Summary: Refactor ClusterDescriptor to support cluster deployment
with job
Key: FLINK-7079
URL: https://issues.apache.org/jira/browse/FLINK-7079
Project: Flink
Till Rohrmann created FLINK-7078:
Summary: Support fencing tokens to filter out outdated messages
Key: FLINK-7078
URL: https://issues.apache.org/jira/browse/FLINK-7078
Project: Flink
Issue Ty
Till Rohrmann created FLINK-7077:
Summary: Implement task release to support dynamic scaling
Key: FLINK-7077
URL: https://issues.apache.org/jira/browse/FLINK-7077
Project: Flink
Issue Type: S
Till Rohrmann created FLINK-7076:
Summary: Add support for dynamic container allocation to
ResourceManager
Key: FLINK-7076
URL: https://issues.apache.org/jira/browse/FLINK-7076
Project: Flink
Till Rohrmann created FLINK-7075:
Summary: Implement Flip-6 standalone mode
Key: FLINK-7075
URL: https://issues.apache.org/jira/browse/FLINK-7075
Project: Flink
Issue Type: New Feature
Till Rohrmann created FLINK-7074:
Summary: Add entry point for TaskManagerRunner
Key: FLINK-7074
URL: https://issues.apache.org/jira/browse/FLINK-7074
Project: Flink
Issue Type: Sub-task
Till Rohrmann created FLINK-7073:
Summary: Create RESTful JobManager endpoint
Key: FLINK-7073
URL: https://issues.apache.org/jira/browse/FLINK-7073
Project: Flink
Issue Type: Sub-task
Till Rohrmann created FLINK-7072:
Summary: Create RESTful cluster endpoint
Key: FLINK-7072
URL: https://issues.apache.org/jira/browse/FLINK-7072
Project: Flink
Issue Type: Sub-task
Till Rohrmann created FLINK-7071:
Summary: Create RESTful client
Key: FLINK-7071
URL: https://issues.apache.org/jira/browse/FLINK-7071
Project: Flink
Issue Type: Sub-task
Components
Big +1 from my side on getting this effort started.
Users have asked for this and I would like to see some progress there.
Did anybody submit a talk about the ML efforts to Flink Forward Berlin this
year?
On Fri, Jun 30, 2017 at 6:04 PM, Fabian Hueske wrote:
> Yes, I know that Theo is engaged i
Yes, that’s definitely possible. I was referring to the fact that this would
break the user-facing API and these are methods declared as @Public, i.e. they
cannot change.
> On 3. Jul 2017, at 18:45, Ted Yu wrote:
>
> Currently StreamExecutionEnvironment exposes Kryo thru the following:
>
> i
Currently StreamExecutionEnvironment exposes Kryo thru the following:
import com.esotericsoftware.kryo.Serializer;
I think shading is possible since we can declare the Serializer class to
come from shaded Kryo namespace.
On Mon, Jul 3, 2017 at 9:25 AM, Aljoscha Krettek
wrote:
> Is it even poss
Is it even possible to shade Kryo with it being in the public API? I don’t
think it is (without looking into this to deeply, though).
> On 3. Jul 2017, at 17:23, Chesnay Schepler wrote:
>
> I would tackle Kryo later as it is exposed through the API
> (StreamExecutionEnvironment#addDefaultKryoS
Hi Simone,
the output of your app is on the task manager in cluster mode, not in client
side.
发自我的 iPad
在 2017年7月3日,23:12,simone sguazza
mailto:simone-sgua...@hotmail.com>> 写道:
Hi, I'm a student and I using flink v1.2.1 to develop a workflow to analyze
data coming from kafka v0.10.
At the
Have we considered using tool(s) such as nailgun ?
https://www.lightbend.com/blog/zinc-and-incremental-compilation
Cheers
On Mon, Jul 3, 2017 at 7:42 AM, Chesnay Schepler wrote:
> Hello,
>
> I want to start a discussion on how we plan to deal with ever-increasing
> build times in the long term
I would tackle Kryo later as it is exposed through the API
(StreamExecutionEnvironment#addDefaultKryoSerializer)
which will make the shading process more difficult than for the modules
that are done so far.
Technically this doesn't prevent us from adding a flink-shaded-kryo2/3
module right now
Hi, I'm a student and I using flink v1.2.1 to develop a workflow to analyze
data coming from kafka v0.10.
At the moment everything work fine, from eclipse I can export the runnable jar
with dependencies and with "sudo java -jar flinkApp.jar" I can run the flink
application on ubuntu server.
U
Other non-Hadoop dependencies that I think are important are the Kryo
dependencies.
Do we want them in the first release, or tackle them later?
Specifically, I think we need
- flink-shaded-kryo2 which includes kryo2 plus chill in the version we
currently use
- flink-shaded-kryo3 which includ
Hello,
I want to start a discussion on how we plan to deal with ever-increasing
build times in the long term.
While the profile reorganization proposed in FLINK-7047 again brings us
below 50 minute build times
it is only a matter of time once we hit the timeout again. There is
already one pr
Chesnay Schepler created FLINK-7070:
---
Summary: Rework
ScalaShellITCase#testSubmissionOfExternalLibraryStream
Key: FLINK-7070
URL: https://issues.apache.org/jira/browse/FLINK-7070
Project: Flink
Chesnay Schepler created FLINK-7069:
---
Summary: Catch exceptions for each reporter separately
Key: FLINK-7069
URL: https://issues.apache.org/jira/browse/FLINK-7069
Project: Flink
Issue Type:
Nico Kruber created FLINK-7068:
--
Summary: change BlobService sub-classes for permanent and
transient BLOBs
Key: FLINK-7068
URL: https://issues.apache.org/jira/browse/FLINK-7068
Project: Flink
I
Thanks for working on this Chesnay.
I think releasing flink-shaded and integrating it in the build before
touching the Hadoop dependencies it sounds like a good plan.
+1
Cheers, Fabian
2017-07-03 14:32 GMT+02:00 Chesnay Schepler :
> Hello,
>
> I would like to kick off the first release of flink
+1
Sounds good! I have followed the process on the various issues and the new
shaded repository and the changes seem straightforward (more or less ;-))
> On 3. Jul 2017, at 14:32, Chesnay Schepler wrote:
>
> Hello,
>
> I would like to kick off the first release of flink-shaded.
>
> In the cu
Hello,
I would like to kick off the first release of flink-shaded.
In the current state the release would include shaded dependencies for
asm, guava and netty.
All changes required for the integration into Flink have been prepared
and tested locally and on yarn.
In order for these changes
Ufuk Celebi created FLINK-7067:
--
Summary: Cancel with savepoint does not restart checkpoint
scheduler on failure
Key: FLINK-7067
URL: https://issues.apache.org/jira/browse/FLINK-7067
Project: Flink
Piotr Nowojski created FLINK-7066:
-
Summary: Kafka integration tests failing in "airplane mode"
Key: FLINK-7066
URL: https://issues.apache.org/jira/browse/FLINK-7066
Project: Flink
Issue Type
Xu Pingyong created FLINK-7065:
--
Summary: separate the flink-streaming-java module from
flink-clients
Key: FLINK-7065
URL: https://issues.apache.org/jira/browse/FLINK-7065
Project: Flink
Issue
hive.travis-ci.org/jobs/248822552/log.txt?X-Amz-Expires=29&X-Amz-Date=20170703T092943Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170703/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=08fc0358d0d322d0df94a899438f2f1b2585335a71f76ef5
txt?X-Amz-Expires=30&X-Amz-Date=20170703T092940Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170703/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=f468cd238236d7038a1e12086dd4a0e3ba538d93c883790d180e4c63b973a5f2
* https://tra
46 matches
Mail list logo