Chengxiang Li created FLINK-3098:
Summary: Cast from Date to Long throw compile error.
Key: FLINK-3098
URL: https://issues.apache.org/jira/browse/FLINK-3098
Project: Flink
Issue Type: Bug
Timo Walther created FLINK-3097:
---
Summary: Add support for custom functions in Table API
Key: FLINK-3097
URL: https://issues.apache.org/jira/browse/FLINK-3097
Project: Flink
Issue Type: New Fea
Thank you Robert, now I can assign myself.
On Wed, Nov 25, 2015 at 1:09 AM, Robert Metzger wrote:
> I added you as a contributor.
>
> On Wed, Nov 25, 2015 at 7:29 AM, jun aoki wrote:
>
> > Hi Henry, thank you for helping. My id is jaoki
> >
> > On Tue, Nov 24, 2015 at 9:47 PM, Henry Saputra
>
Robert Metzger created FLINK-3096:
-
Summary: ChaosMonkeyITCase fails in checkCleanRecoveryState with
Unclean checkpoints
Key: FLINK-3096
URL: https://issues.apache.org/jira/browse/FLINK-3096
Project:
Robert Metzger created FLINK-3095:
-
Summary: Test
ZooKeeperLeaderElectionTest.testZooKeeperReelectionWithReplacement unstable
Key: FLINK-3095
URL: https://issues.apache.org/jira/browse/FLINK-3095
Proj
Slots are like "resource groups" which execute entire pipelines. They
frequently have more than one operator.
What you can try as a workaround is decrease the number of slots per
machine to cause the operators to be spread across more machines.
If this is a crucial issue for your use case, it sho
> On 01 Dec 2015, at 15:26, Kashmar, Ali wrote:
>
> Is there a way to make a task cluster-parallelizable? I.e. Make sure the
> parallel instances of the task are distributed across the cluster. When I
> run my flink job with a parallelism of 16, all the parallel tasks are
> assigned to the first
Is there a way to make a task cluster-parallelizable? I.e. Make sure the
parallel instances of the task are distributed across the cluster. When I
run my flink job with a parallelism of 16, all the parallel tasks are
assigned to the first task manager.
- Ali
On 2015-11-30, 2:18 PM, "Ufuk Celebi"
I left out the classes in memory except for the Input/Output views.
Or course, we should try to minimize the stable classes, but user programs
get a lot of extension points in Flink ;)
I've opened a pull request with my current suggestion:
https://github.com/apache/flink/pull/1426
On Tue, Dec 1
Till Rohrmann created FLINK-3094:
Summary: FileStateBackend does not clean up job-id checkpoint
directory
Key: FLINK-3094
URL: https://issues.apache.org/jira/browse/FLINK-3094
Project: Flink
Thanks for the explanation. I was just wondering how you approached
the problem. Going through class-by-class makes sense.
Not sure whether we want to make "org.apache.flink.core.memory" and
"org.apache.flink.api.common.distributions" stable interfaces. I would
think these qualify more as experime
Robert Metzger created FLINK-3093:
-
Summary: Introduce annotations for interface stability
Key: FLINK-3093
URL: https://issues.apache.org/jira/browse/FLINK-3093
Project: Flink
Issue Type: New
12 matches
Mail list logo