Hi,
I am trying to run an infinite streaming job (ie, one that does not
terminate because it is generating output date randomly on the fly). I
kill this job with .stop() or .shutdown() method of
ForkableFlinkMiniCluster.
I did not find any example using a similar setup. In the provided
examples,
Stephan Ewen created FLINK-1796:
---
Summary: Local mode TaskManager should have a process reaper
Key: FLINK-1796
URL: https://issues.apache.org/jira/browse/FLINK-1796
Project: Flink
Issue Type: B
Stephan Ewen created FLINK-1795:
---
Summary: Solution set allows duplicates upon construction.
Key: FLINK-1795
URL: https://issues.apache.org/jira/browse/FLINK-1795
Project: Flink
Issue Type: Bug
+1
Developers that solve the problem by fixing the issue should change
the status to "Resolved" and the person who create the issue could
change the status to "Closed" to verify.
- Henry
On Fri, Mar 27, 2015 at 6:52 AM, Maximilian Michels wrote:
> Hmm. In my eyes, "Closed" is for one-time issu
Till Rohrmann created FLINK-1794:
Summary: Add test base for scalatest and adapt flink-ml test cases
Key: FLINK-1794
URL: https://issues.apache.org/jira/browse/FLINK-1794
Project: Flink
Issue
+1 for 0.9.0-milestone-1
On Fri, Mar 27, 2015 at 3:52 PM, Kostas Tzoumas wrote:
> +1
>
> On Fri, Mar 27, 2015 at 3:44 PM, Aljoscha Krettek
> wrote:
>
> > +1 for 0.9.0-M1 (or milestone-1)
> > On Mar 27, 2015 2:45 PM, "Ufuk Celebi" wrote:
> >
> > > On Friday, March 27, 2015, Maximilian Michels
+1
On Fri, Mar 27, 2015 at 3:44 PM, Aljoscha Krettek
wrote:
> +1 for 0.9.0-M1 (or milestone-1)
> On Mar 27, 2015 2:45 PM, "Ufuk Celebi" wrote:
>
> > On Friday, March 27, 2015, Maximilian Michels wrote:
> >
> > > +1 for 0.9.0-milestone-1
> > >
> >
> > +1
> >
>
+1 for 0.9.0-M1 (or milestone-1)
On Mar 27, 2015 2:45 PM, "Ufuk Celebi" wrote:
> On Friday, March 27, 2015, Maximilian Michels wrote:
>
> > +1 for 0.9.0-milestone-1
> >
>
> +1
>
Hmm. In my eyes, "Closed" is for one-time issues that are not likely to
occur again. "Resolved" is to mark the issue as resolved with possible
issues coming up in the course of usage or testing. I would say, "Closed"
is more from an end-user perspective, whereas "Resolved" marks the
developer's res
On Friday, March 27, 2015, Maximilian Michels wrote:
> +1 for 0.9.0-milestone-1
>
+1
@Vasia: I don't know. I use "Closed" for issues which are invalid or won't
fix.
Resolved for those that were implemented.
On Wed, Mar 18, 2015 at 2:57 PM, Vasiliki Kalavri wrote:
> Thanks for this Robert! I updated the gelly-related closed issues.
> BTW, what's the difference between closed and
+1 for 0.9.0-milestone-1
+1 for 0.9.0-milestone-1
On Fri, Mar 27, 2015 at 12:50 PM, Márton Balassi
wrote:
> +1 for 0.9.0-milestone-1.
>
> On Fri, Mar 27, 2015 at 12:47 PM, Stephan Ewen wrote:
>
> > Okay, to how about we make this
> >
> >
> > org.apache.flink
> > flink-core
> > 0.9.0-milestone-1
> >
> >
> > I think it
+1 for 0.9.0-milestone-1.
On Fri, Mar 27, 2015 at 12:47 PM, Stephan Ewen wrote:
> Okay, to how about we make this
>
>
> org.apache.flink
> flink-core
> 0.9.0-milestone-1
>
>
> I think it is common that milestones have numbers. There is no such thing
> as "the" milestone.
>
>
>
> On Thu, Mar 26
Okay, to how about we make this
org.apache.flink
flink-core
0.9.0-milestone-1
I think it is common that milestones have numbers. There is no such thing
as "the" milestone.
On Thu, Mar 26, 2015 at 10:02 PM, Henry Saputra
wrote:
> Yeah, always prefer to get it with consensus that VOTE
>
> I
Maximilian Michels created FLINK-1793:
-
Summary: Streaming jobs can't be canceled
Key: FLINK-1793
URL: https://issues.apache.org/jira/browse/FLINK-1793
Project: Flink
Issue Type: Bug
Robert Metzger created FLINK-1792:
-
Summary: Improve TM Monitoring: CPU utilization, hide graphs by
default and show summary only
Key: FLINK-1792
URL: https://issues.apache.org/jira/browse/FLINK-1792
17 matches
Mail list logo
