Generally, for bugfix releases I only regard issues as blockers that
were introduced in that version, which doesn't appear to be the case here.
There's nothing speaking against another bugfix release soon after 1.5.3
once the issue is resolved.
On 16.08.2018 18:46, Elias Levy wrote:
If I
If I may, think FLINK-10011 should be considered a blocker and included in
1.5.3 and a 1.4.3 release.
On Thu, Aug 16, 2018 at 3:09 AM Dominik Wosiński wrote:
> +1, I agree that frequent releases are good for users.
> Dominik
>
>
> Wysłane z aplikacji Poczta dla Windows 10
>
> Od: Stefan Richter
Till Rohrmann created FLINK-10164:
-
Summary: Add support for resuming from savepoints to
StandaloneJobClusterEntrypoint
Key: FLINK-10164
URL: https://issues.apache.org/jira/browse/FLINK-10164
I agree with Dominik. We could add this test to
`flink-end-to-end-test/run-pre-commit-tests.sh` or
`flink-end-to-end-test/run-nightly-tests.sh` like we did for the
`flink-end-to-end-test/test-scripts/test_docker_embedded_job.sh` and
Timo Walther created FLINK-10163:
Summary: Support CREATE VIEW in SQL Client
Key: FLINK-10163
URL: https://issues.apache.org/jira/browse/FLINK-10163
Project: Flink
Issue Type: New Feature
xymaqingxiang created FLINK-10162:
-
Summary: Add host in checkpoint detail
Key: FLINK-10162
URL: https://issues.apache.org/jira/browse/FLINK-10162
Project: Flink
Issue Type: Improvement
xymaqingxiang created FLINK-10161:
-
Summary: Add host in checkpoint detail
Key: FLINK-10161
URL: https://issues.apache.org/jira/browse/FLINK-10161
Project: Flink
Issue Type: New Feature
Zdenek created FLINK-10160:
--
Summary: Index out of bound when serializing operator state
Key: FLINK-10160
URL: https://issues.apache.org/jira/browse/FLINK-10160
Project: Flink
Issue Type: Bug
Imho,
Such tests should be off by default as they impose some requirements on the
people trying to build Flink from source. And one would have to install docker
only for the tests to pass. But of course they should be enabled for CI builds.
Best Regards,
Dominik.
Wysłane z aplikacji Poczta
Hi,
I'm working together with Richard Deurwaarder on the PubSub Source and Sink
https://issues.apache.org/jira/browse/FLINK-9311
We currently have most of the code done and we also have several tests that
verify the behavior by actually reading and writing messages to and from
PubSub.
These
Piotr Nowojski created FLINK-10159:
--
Summary: TestHarness#initializeState(xyz) calls after
TestHarness#open() are being silently ignored
Key: FLINK-10159
URL: https://issues.apache.org/jira/browse/FLINK-10159
Hi everyone,
Please review and vote on the release candidate #1 for the version
1.5.3, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes
+1, I agree that frequent releases are good for users.
Dominik
Wysłane z aplikacji Poczta dla Windows 10
Od: Stefan Richter
Wysłano: czwartek, 16 sierpnia 2018 10:57
Do: dev
Temat: Re: [DISCUSS] Release Flink 1.5.3
+1 sounds good.
Stefan
> Am 16.08.2018 um 09:55 schrieb Piotr Nowojski :
>
>
+1 sounds good.
Stefan
> Am 16.08.2018 um 09:55 schrieb Piotr Nowojski :
>
> +1 from me
>
> Piotrek
>
>> On 16 Aug 2018, at 09:40, Timo Walther wrote:
>>
>> Thank you for starting this discussion.
>>
>> +1 for this
>>
>> Regards,
>> Timo
>>
>> Am 16.08.18 um 09:27 schrieb vino yang:
>>>
aitozi created FLINK-10158:
--
Summary: The DataOutputSerializer may consume excessive memory
Key: FLINK-10158
URL: https://issues.apache.org/jira/browse/FLINK-10158
Project: Flink
Issue Type:
chengjie.wu created FLINK-10157:
---
Summary: The TTL state not allow `null` state value
Key: FLINK-10157
URL: https://issues.apache.org/jira/browse/FLINK-10157
Project: Flink
Issue Type: Bug
+1 from me
Piotrek
> On 16 Aug 2018, at 09:40, Timo Walther wrote:
>
> Thank you for starting this discussion.
>
> +1 for this
>
> Regards,
> Timo
>
> Am 16.08.18 um 09:27 schrieb vino yang:
>> Agree! This sounds very good.
>>
>> Till Rohrmann 于2018年8月16日周四 下午3:14写道：
>>
>>> +1 for
Thank you for starting this discussion.
+1 for this
Regards,
Timo
Am 16.08.18 um 09:27 schrieb vino yang:
Agree! This sounds very good.
Till Rohrmann 于2018年8月16日周四 下午3:14写道：
+1 for starting the release process 1.5.3 immediately. We can always
create another bug fix release afterwards. I
Agree! This sounds very good.
Till Rohrmann 于2018年8月16日周四 下午3:14写道：
> +1 for starting the release process 1.5.3 immediately. We can always
> create another bug fix release afterwards. I think the more often we
> release the better it is for our users, because they receive incremental
>
+1 for starting the release process 1.5.3 immediately. We can always create
another bug fix release afterwards. I think the more often we release the
better it is for our users, because they receive incremental improvements
faster.
Cheers,
Till
On Thu, Aug 16, 2018 at 8:52 AM Chesnay Schepler
I would actually start with the release process today unless anyone objects.
On 16.08.2018 08:46, vino yang wrote:
Hi Chesnay,
+1
I want to know when you plan to cut the branch.
Thanks, vino.
Chesnay Schepler 于2018年8月16日周四 下午2:29写道：
Hello everyone,
it has been a little over 2 weeks
Hi Chesnay,
+1
I want to know when you plan to cut the branch.
Thanks, vino.
Chesnay Schepler 于2018年8月16日周四 下午2:29写道：
> Hello everyone,
>
> it has been a little over 2 weeks since 1.5.2 was released, and since
> then a number of fixes were added to the release-1.5 that I think we
> should
Hello everyone,
it has been a little over 2 weeks since 1.5.2 was released, and since
then a number of fixes were added to the release-1.5 that I think we
should push to users.
Notable fixes, (among others) are FLINK-9969 which fixes a memory leak
when using batch, FLINK-10066 that reduces
23 matches
Mail list logo
