Hi everyone,
Please review and vote on the release candidate #3 for the version 1.3.2, 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],
Nico Chen created FLINK-7368:
Summary: MetricStore makes cpu spin at 100%
Key: FLINK-7368
URL: https://issues.apache.org/jira/browse/FLINK-7368
Project: Flink
Issue Type: Bug
Components
Bowen Li created FLINK-7367:
---
Summary: Parameterize FlinkKinesisProducer on
RecordMaxBufferedTime, MaxConnections, RequestTimeout, and more
Key: FLINK-7367
URL: https://issues.apache.org/jira/browse/FLINK-7367
Bowen Li created FLINK-7366:
---
Summary: Upgrade kinesis-producer-library in
flink-connector-kinesis from 0.10.2 to 0.12.5
Key: FLINK-7366
URL: https://issues.apache.org/jira/browse/FLINK-7366
Project: Flink
Bowen Li created FLINK-7365:
---
Summary: warning of attempt to override final parameter:
fs.s3.buffer.dir
Key: FLINK-7365
URL: https://issues.apache.org/jira/browse/FLINK-7365
Project: Flink
Issue T
Thanks for testing everyone. Unfortunately, I have to close this vote because
of the problem with the Gelly Examples jar. I'll immediately create another RC
(in fact I'm already on it). I'm hoping that we can do an expedited vote on
that new RC because the only change in that RC is going to be a
Elias Levy created FLINK-7364:
-
Summary: Log exceptions from user code in streaming jobs
Key: FLINK-7364
URL: https://issues.apache.org/jira/browse/FLINK-7364
Project: Flink
Issue Type: Bug
Till, with (c) are you suggesting that we'd use Akka 2.3 for Scala 2.10 and
Akka 2.4+ for Scala 2.11+? Sounds reasonable but I don't know how
feasible it is. I will say I'm optimistic because a) Akka 2.4 is said to
be binary compatible, and b) the Flakka fork appears to be subsumed by 2.4.
Let
Hello,
I would like to know if we have any latency requirements for choosing
appropriate state backend?
For example, if an HCFS implementation is used as Flink state backend (instead
of stock HDFS), are there any implications that one needs to know with respect
to the performance?
- Frequency o
I haven't followed this discussion in detail nor am I familiar with
the service authorization topic or Flakka, but a) sounds like a lot of
maintenance work to me.
If possible I would go with c) and maybe start a discussion about
dropping Scala 2.10 support to check whether that is a viable option
+1
- checked hashes and signatures
- checked added and modified dependencies since Flink 1.3.1
- io.dropwizard.metrics/metrics-core was upgraded to 3.1.5 and is ASL
- org.xerial.snappy/snappy-java/1.0.5 was added and is ASL
- built from source
Thanks, Fabian
2017-08-03 11:24 GMT+02:00 Stefa
Alternatively there would also be an option
c) only support mutual auth for Akka 2.4+ if the backport is unrealistic to
do
But this of course would break security for Scala 2.10. On the other hand
people are already using Flink without this feature.
Cheers,
Till
On Wed, Aug 2, 2017 at 7:21 PM,
Nico Kruber created FLINK-7363:
--
Summary: add hashes and signatures to the download page
Key: FLINK-7363
URL: https://issues.apache.org/jira/browse/FLINK-7363
Project: Flink
Issue Type: Improvem
Aljoscha Krettek created FLINK-7362:
---
Summary: CheckpointProperties are not correctly set when restoring
savepoint with HA enabled
Key: FLINK-7362
URL: https://issues.apache.org/jira/browse/FLINK-7362
+1
1. Cluster tests
Tested with the stateful state machine job on the following settings:
- Cloud env: AWS
- Distributions: EMR 5.7.0
- Flink deployment method: YARN (Hadoop 2.7.2)
- HA: enabled
- Kerberos: disabled
- Kafka version: 0.10, 0.11
- State Backends: Heap (Sync / Async) & RocksDB (incr
Nico Kruber created FLINK-7361:
--
Summary: flink-web doesn't build with ruby 2.4
Key: FLINK-7361
URL: https://issues.apache.org/jira/browse/FLINK-7361
Project: Flink
Issue Type: Bug
Com
Timo Walther created FLINK-7360:
---
Summary: Support Scala map type
Key: FLINK-7360
URL: https://issues.apache.org/jira/browse/FLINK-7360
Project: Flink
Issue Type: New Feature
Componen
yf created FLINK-7359:
-
Summary: flink-storm should update ComponentConfiguration to
stormConfig
Key: FLINK-7359
URL: https://issues.apache.org/jira/browse/FLINK-7359
Project: Flink
Issue Type: Bug
18 matches
Mail list logo