I've had a private conversation with Martin to further work on this issue.
The problem is that "flink-neo4j" is using jersey-client, version 1.19
(Neo4j is also using that version). Our flink-shaded-hadoop2 jar contains a
jersey-client version 1.9, which appears first in the classpath, to the JVM
Thanks Fabian for drafting the release announcement. The release
artifacts have already been synced and I've updated the website for
the 0.10.0 release.
Seems like we are set up to publish the release announcement later today.
On Fri, Nov 13, 2015 at 1:41 PM, Ufuk Celebi wrote:
> https://cwiki.a
Not that I am aware of. This is most probably a bug.
Looking at the code of the ExecutionGraph:
A job can only be cancelled when the job status is CREATED or RUNNING. If the
job failed during execution it is in state FAILED until it is RESTARTING. After
resetting the ExecutionGraph state, the s
Gyula Fora created FLINK-3011:
-
Summary: Cannot cancel failing/restarting streaming job from the
command line
Key: FLINK-3011
URL: https://issues.apache.org/jira/browse/FLINK-3011
Project: Flink
Hey,
Is there any other way to cancel a job besides ./bin/flink cancel jobId?
This doesnt seem to work when a job cannot be scheduled and is retrying
over and over again.
The exception I get:
13:58:11,240 INFO org.apache.flink.runtime.jobmanager.JobManager
- Status of job 0c895d22c632
https://cwiki.apache.org/confluence/display/FLINK/Migration+Guide%3A+0.9.x+to+0.10.x
> On 13 Nov 2015, at 10:42, Fabian Hueske wrote:
>
> Yes, that's a good idea. I would go for a wiki page that we link to from
> the announcement.
> I don't think this level of detail should to go directly into t
Have a look at my updated version of your code:
https://github.com/rmetzger/scratch/tree/dependency_problem
It now executes both tests, however, I was not able to get the second test
to pass. It seems that Neo4j's web server is returning a 500 status code
when open()'ing the connection.
I'm not sur
Fabian Hueske created FLINK-3010:
Summary: Add link to powered-by wiki page to project website
Key: FLINK-3010
URL: https://issues.apache.org/jira/browse/FLINK-3010
Project: Flink
Issue Type:
Ufuk Celebi created FLINK-3009:
--
Summary: Cannot build docs with Jekyll 3.0.0
Key: FLINK-3009
URL: https://issues.apache.org/jira/browse/FLINK-3009
Project: Flink
Issue Type: Bug
Compo
Gyula Fora created FLINK-3008:
-
Summary: Failing/restarting streaming jobs are buggy in the
webfrontend
Key: FLINK-3008
URL: https://issues.apache.org/jira/browse/FLINK-3008
Project: Flink
Issue
I was thinking about this issue too and wanted to include it in my
current PR (I just about to rebase it to the current master...
https://github.com/apache/flink/pull/750).
Or should be open a new JIRA for it and address it after Stop signal is
available?
-Matthias
On 11/12/2015 11:47 AM, Maxim
Yes, that's a good idea. I would go for a wiki page that we link to from
the announcement.
I don't think this level of detail should to go directly into the release
announcement.
It would be great if you could draft a migration guide.
2015-11-13 10:27 GMT+01:00 Ufuk Celebi :
>
> > On 12 Nov 2015
> On 12 Nov 2015, at 21:25, Fabian Hueske wrote:
>
> Hi everybody,
>
> with 0.10.0 almost being released I started writing release nodes for the
> Flink blog.
>
> Please find the current draft here:
> https://docs.google.com/document/d/1ULZAdxwneZAldhJ69tB3UEvjJQhS-ZASN5mdtumtJ48/edit?usp=shar
Great. Thanks Max! :)
> On Nov 13, 2015, at 4:06 PM, Vasiliki Kalavri
> wrote:
>
> \o/ \o/ \o/
> Thank you Max!
> On Nov 13, 2015 2:23 AM, "Nick Dimiduk" wrote:
>
>> Woo hoo!
>>
>> On Thu, Nov 12, 2015 at 3:01 PM, Maximilian Michels
>> wrote:
>>
>>> Thanks for voting! The vote passes.
>>>
14 matches
Mail list logo
