Ufuk Celebi created FLINK-2793:
--
Summary: Redirect to leading JobManager web fronted in
non-standalone mode
Key: FLINK-2793
URL: https://issues.apache.org/jira/browse/FLINK-2793
Project: Flink
Ufuk Celebi created FLINK-2792:
--
Summary: Set log level of actor messages to TRACE
Key: FLINK-2792
URL: https://issues.apache.org/jira/browse/FLINK-2792
Project: Flink
Issue Type: Wish
Sachin Goel created FLINK-2791:
--
Summary: ParallelMergeITCase failure
Key: FLINK-2791
URL: https://issues.apache.org/jira/browse/FLINK-2791
Project: Flink
Issue Type: Bug
Components: T
Till Rohrmann created FLINK-2790:
Summary: Add high availability support for Yarn
Key: FLINK-2790
URL: https://issues.apache.org/jira/browse/FLINK-2790
Project: Flink
Issue Type: Sub-task
Yes, exactly. Then, I do not think FLINK-2443 is a blocker for graduating
On Wed, Sep 30, 2015 at 11:09 AM, Vasiliki Kalavri <
vasilikikala...@gmail.com> wrote:
> If by workaround you mean setting the solutionSetUnmanaged option, yes that
> works, because the CompactingHashTable is skipped.
>
> -
If by workaround you mean setting the solutionSetUnmanaged option, yes that
works, because the CompactingHashTable is skipped.
-V.
On 30 September 2015 at 10:44, Ufuk Celebi wrote:
>
> > On 30 Sep 2015, at 10:06, Kostas Tzoumas wrote:
> >
> > Does the workaround work, or can FLINK-2443 still a
> On 30 Sep 2015, at 10:06, Kostas Tzoumas wrote:
>
> Does the workaround work, or can FLINK-2443 still appear?
>
> If we have a workaround, we can schedule a fix to FLINK-2443 for 0.10.1
+1 Sounds like a good plan to me.
– Ufuk
Does the workaround work, or can FLINK-2443 still appear?
If we have a workaround, we can schedule a fix to FLINK-2443 for 0.10.1
On Tue, Sep 29, 2015 at 9:59 PM, Vasiliki Kalavri wrote:
> Hello squirrels,
>
> since it was already mentioned in the other thread, I'm starting this
> discussion to