Hey,
This little screencast shows how to run WordCount in IntelliJ.
Note that it will take a bit more time the first time because IntelliJ will
compile all required classes:
https://www.youtube.com/watch?v=JIV_rX-OIQM&feature=youtu.be
Let us know if you need more help.
Robert
On Fri, Mar 6, 2015
The failing test is the
JobManagerStartupTest.testJobManagerStartupFails(JobManagerStartupTest.java:93)
Am 04.03.2015 21:47 schrieb "Henry Saputra (JIRA)" :
> Henry Saputra created FLINK-1651:
>
>
> Summary: Running mvn test got stuck
>
Hey all,
I'm currently working a lot on the UDF static code analyzer. But I have
a general question about Semantic Properties which might be also
interesting for other users.
How is the ForwardedFields annotation interpreted for UDF functions with
Iterables?
An example can be found in:
or
Hi Timo,
there are several restrictions for forwarded fields of operators with
iterator input.
1) forwarded fields must be emitted in the order in which they are received
through the iterator
2) all forwarded fields of a record must stick together, i.e., if your
function builds record from field 0
Fabian Hueske created FLINK-1656:
Summary: Fix ForwardedField documentation for operators with
iterator input
Key: FLINK-1656
URL: https://issues.apache.org/jira/browse/FLINK-1656
Project: Flink
Thanks Robert.
> On Mar 6, 2015, at 1:41 PM, Robert Metzger wrote:
>
> Hey,
>
> This little screencast shows how to run WordCount in IntelliJ.
> Note that it will take a bit more time the first time because IntelliJ will
> compile all required classes:
> https://www.youtube.com/watch?v=JIV_rX-O
Hey Dulaj!
Examples should run in a straight forward way from the IDE.
The readme (displayed at the bottom of the page) has a bit of info on IDE
setup https://github.com/apache/flink
One thing you may have to do (if you compile the Scala project) is to
configure the macroparadise compiler plugin
Thank you all. IntelliJ shows "Unregister task with execution ID (something)”
couple of times in the output. But I guess it’s normal?
> On Mar 6, 2015, at 4:08 PM, Stephan Ewen wrote:
>
> Hey Dulaj!
>
> Examples should run in a straight forward way from the IDE.
>
> The readme (displayed at t
I think the order of emitting elements is not part of the forward field
properties, but would rather be a separate one that we do not have right
now.
At the moment, we would assume that all group operations destroy secondary
orders.
In that sense, forward fields in group operations only make sens
Yes, this means that a task has finished its computation and can be removed
from the TaskManager.
On Fri, Mar 6, 2015 at 11:44 AM, Dulaj Viduranga
wrote:
> Thank you all. IntelliJ shows "Unregister task with execution ID
> (something)” couple of times in the output. But I guess it’s normal?
>
>
Gyula Fora created FLINK-1657:
-
Summary: Make count windows local automatically
Key: FLINK-1657
URL: https://issues.apache.org/jira/browse/FLINK-1657
Project: Flink
Issue Type: Improvement
Thanks Stephan, just noticed that line.
Seemed like there was issue in Akka 2.1.x where awaitTermination hang
when there is remote actors.
Need to check Akka version in my box.
- Henry
On Fri, Mar 6, 2015 at 1:11 AM, Stephan Ewen wrote:
> The failing test is the
> JobManagerStartupTest.testJob
Gyula Fora created FLINK-1658:
-
Summary: Rename AbstractEvent to AbstractTaskEvent and
AbstractJobEvent
Key: FLINK-1658
URL: https://issues.apache.org/jira/browse/FLINK-1658
Project: Flink
Issue
Hi,
Is there a way to turn off JobManager and TaskManager messages in the output?
(Only example outputs).
Maybe a flag?
> On Mar 6, 2015, at 4:45 PM, Till Rohrmann wrote:
>
> Yes, this means that a task has finished its computation and can be removed
> from the TaskManager.
>
> On Fri, Mar 6,
Well, I need my morning coffee, just remember mvn will pull the right
version of akka appropriately.
The problem is that the BlobManager is started properly since my
machine somehow have "/does-not-exist-no-sir/" directory which is used
as target directory for the BlobSever which should fail.
The
Ah, yeah, that is a vulnerability in the test. Same thing as in the other
test. It gets created because you have root access and the test assumes it
cannot be created.
Safe thing to do is like in your other fix: create a directory where the
user has no write permissions and set this to the BLOB st
Thanks Stephan, will send PR for it
On Friday, March 6, 2015, Stephan Ewen wrote:
> Ah, yeah, that is a vulnerability in the test. Same thing as in the other
> test. It gets created because you have root access and the test assumes it
> cannot be created.
>
> Safe thing to do is like in your oth
Henry Saputra created FLINK-1659:
Summary: Rename classes and packages that contains Pact
Key: FLINK-1659
URL: https://issues.apache.org/jira/browse/FLINK-1659
Project: Flink
Issue Type: Task
18 matches
Mail list logo
