That's the right attitude :)
Since one month has passed since my initial email on the 1.3 release,
here's a quick reminder for everybody that we have the following deadlines:
*Feature freeze (branch forking)*: 1 May 2017 (*8 weeks from now*)
*Code freeze (first voting RC)*: 15 May 2017
*Release
Aljoscha Krettek created FLINK-5967:
---
Summary: Document AggregatingState
Key: FLINK-5967
URL: https://issues.apache.org/jira/browse/FLINK-5967
Project: Flink
Issue Type: Improvement
Aljoscha Krettek created FLINK-5968:
---
Summary: Document WindowedStream.aggregate()
Key: FLINK-5968
URL: https://issues.apache.org/jira/browse/FLINK-5968
Project: Flink
Issue Type: Improveme
Aljoscha Krettek created FLINK-5969:
---
Summary: Add savepoint backwards compatibility tests from 1.2 to
1.3
Key: FLINK-5969
URL: https://issues.apache.org/jira/browse/FLINK-5969
Project: Flink
Chesnay Schepler created FLINK-5970:
---
Summary: Job-/TaskManagerStartupTest may run indefinitely
Key: FLINK-5970
URL: https://issues.apache.org/jira/browse/FLINK-5970
Project: Flink
Issue Ty
A singular "all reformat in one instant" will cause immense damage to the
project, in my opinion.
- There are so many pull requests that we are having a hard time keeping
up, and merging will a lot more time intensive.
- I personally have many forked branches with WIP features that will
probab
Looks good to me!
On Mon, Mar 6, 2017 at 10:55 AM, Robert Metzger wrote:
> That's the right attitude :)
>
> Since one month has passed since my initial email on the 1.3 release,
> here's a quick reminder for everybody that we have the following deadlines:
>
> *Feature freeze (branch forking)*:
Hi Folks,
I would like to finally agree on a plan for implementing side inputs in
Flink. There has already been an attempt to come to consensus [1], which
resulted in two design documents. I tried to consolidate those two and
also added a section about implementation plans. This is the resulting
F
Hi Aljoscha,
Thank you for the nice proposal!
I think it would make sense to allow user's to affect the readiness of the
side input. I think making it ready when the first element arrives is only
slightly better then making it always ready from usability perspective. For
instance if I am joining
Hi,
I was looking over the travis test& deploy status (because of a fail that was
unrelated with my contribution in the pull request). I see a lot of failures
also for the other pull requests.
I see that there are typical for 2 build jobs that fail across pull requests:
one related to the fact
Till Rohrmann created FLINK-5971:
Summary: JobLeaderIdService should time out registered jobs
Key: FLINK-5971
URL: https://issues.apache.org/jira/browse/FLINK-5971
Project: Flink
Issue Type:
Aljoscha Krettek created FLINK-5972:
---
Summary: Don't allow shrinking merging windows
Key: FLINK-5972
URL: https://issues.apache.org/jira/browse/FLINK-5972
Project: Flink
Issue Type: Bug
Nico Kruber created FLINK-5973:
--
Summary: check whether the direct memory size is always correctly
calculated
Key: FLINK-5973
URL: https://issues.apache.org/jira/browse/FLINK-5973
Project: Flink
Thanks everyone for the reply.
@Xiaogang design document looks very good, looking forward to check the
implementation and to try it out. I see that hdfs:// is mentioned as the
backend storage in the documentation, what about s3://. Is it something
that needed to be considered in the design, or is
Eron Wright created FLINK-5974:
---
Summary: Support Mesos DNS
Key: FLINK-5974
URL: https://issues.apache.org/jira/browse/FLINK-5974
Project: Flink
Issue Type: Improvement
Components: C
Addison Higham created FLINK-5975:
-
Summary: Mesos should support adding volumes to launched
taskManagers
Key: FLINK-5975
URL: https://issues.apache.org/jira/browse/FLINK-5975
Project: Flink
liuyuzhong7 created FLINK-5976:
--
Summary: refactoring remove duplicate Tokenizer in flink-test
Key: FLINK-5976
URL: https://issues.apache.org/jira/browse/FLINK-5976
Project: Flink
Issue Type: Im
17 matches
Mail list logo
