-1 Changing the memory consumption between minor releases should not happen.
The good news: Robert ran a test with the latest 1.1 branch that
contains a fix for the changed RocksDB memory configuration and
reported stable behaviour.
@Flavio: I agree, but since we're already very late with this bu
Ok Ufuk, It's not so urgent indeed ;)
Thanks anyway
On Mon, Dec 19, 2016 at 11:18 AM, Ufuk Celebi wrote:
> -1 Changing the memory consumption between minor releases should not
> happen.
>
> The good news: Robert ran a test with the latest 1.1 branch that
> contains a fix for the changed RocksDB
This vote has been cancelled in favour of RC4.
I will kick of RC4 immediately since all fixes are already in the
release-1.1 branch.
On Tue, Dec 13, 2016 at 11:04 PM, Ufuk Celebi wrote:
> Dear Flink community,
>
> Please vote on releasing the following candidate as Apache Flink version
> 1.1.4.
Aljoscha Krettek created FLINK-5366:
---
Summary: Add end-to-end tests for Savepoint Backwards Compatibility
Key: FLINK-5366
URL: https://issues.apache.org/jira/browse/FLINK-5366
Project: Flink
David Anderson created FLINK-5367:
-
Summary: restore updates lost when merging recent doc refactoring
Key: FLINK-5367
URL: https://issues.apache.org/jira/browse/FLINK-5367
Project: Flink
Issu
Sendoh created FLINK-5368:
-
Summary: Let Kafka consumer show something when it fails to read
one topic out of topic list
Key: FLINK-5368
URL: https://issues.apache.org/jira/browse/FLINK-5368
Project: Flink
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink version 1.1.4.
The commit to be voted on:
8fb0fc8 (http://git-wip-us.apache.org/repos/asf/flink/commit/8fb0fc8)
Branch:
release-1.1.4-rc4
(https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=sho
Hi,
I'm wondering how we want to maintain the ElasticSearch sinks in Flink.
Right now, we have two connectors, supporting the 1.x and 2.x versions.
There is a pending PR [1] for adding ES 5 support.
All three connectors share a lot of code, and there is a pull request [2]
improving the ES 2.x con
Thanks for looking into this Robert.
I agree, it would be good to share as much code as possible between the
Elasticsearch connectors.
+1 for flink-connector-elasticsearch-base
+1 for keeping the connectors in Flink
2016-12-19 16:46 GMT+01:00 Robert Metzger :
> Hi,
> I'm wondering how we want to
Stephan Ewen created FLINK-5369:
---
Summary: jsr305 and logging dependencies should be 'provided' by
default
Key: FLINK-5369
URL: https://issues.apache.org/jira/browse/FLINK-5369
Project: Flink
Hi all!
With having reached the feature freeze points, the 1.2 release branch
should be forked any moment off now.
I would like to merge the FLIP-6 feature branch after the release branch
has been forked off
If anyone has reservations, please let me know.
Summary about the feature branch
- Fu
shijinkui created FLINK-5370:
Summary: build failure for unit test of FileInputFormatTest and
GlobFilePathFilterTest
Key: FLINK-5370
URL: https://issues.apache.org/jira/browse/FLINK-5370
Project: Flink
Hi,
We are currently exploring on building a streaming SQL solution on top of
Flink. We think that Flink is a good fit for the problem.
I'm curious about what is the status on the Flink-Calcite integration right
now? Is it being actively developed and on the road map?
We are also very open to co
13 matches
Mail list logo
