Ah, I see. Yes, that should definitely be good enough (at least for a first
pass).
Do you know how most users tend to deploy and use Flink in practice?
Job-scoped clusters seem preferable for many reasons, but it's possible
that that's only really practical when using YARN/Kubernetes/Mesos. Would
Chesnay Schepler created FLINK-8241:
---
Summary: Remove ResultPartitionWriter related PrepareForTest
annotations
Key: FLINK-8241
URL: https://issues.apache.org/jira/browse/FLINK-8241
Project: Flink
Timo Walther created FLINK-8240:
---
Summary: Create unified interfaces to configure and instatiate
TableSources
Key: FLINK-8240
URL: https://issues.apache.org/jira/browse/FLINK-8240
Project: Flink
+1
- Staged Apache source & binary convenience releases looks good
- Built from source (macOS w/ Scala 2.11, hadoop-free, hadoop-2.8)
- Locally tested topic regex subscription for the Kafka consumer
- Quickstart projects looks good
Other things verified that are carried from previous RC votes
-
Chesnay Schepler created FLINK-8239:
---
Summary: Extend StreamTaskTestHarness to support TwoInput head
operators
Key: FLINK-8239
URL: https://issues.apache.org/jira/browse/FLINK-8239
Project: Flink
Chesnay Schepler created FLINK-8238:
---
Summary: StreamTaskTestHarness should only allow one setup call
Key: FLINK-8238
URL: https://issues.apache.org/jira/browse/FLINK-8238
Project: Flink
+1 (binding)
- build the source locally
- run various table programs
- checked the resource consumption of table programs with retention
enabled and disabled
- built a quickstart project
- tested the web ui submission (found
https://issues.apache.org/jira/browse/FLINK-8187 but this is
Gábor Hermann created FLINK-8237:
Summary: BucketingSink throws NPE when Writer.duplicate returns
null
Key: FLINK-8237
URL: https://issues.apache.org/jira/browse/FLINK-8237
Project: Flink
+1 (binding)
- checked contents of flink-dist for unshaded dependencies
- ran python examples (with/-out arguments) locally
- ran jobs on yarn on a cluster testing optional hadoop dependency
- verified that quickstarts work
- checked JM/TM logs for anything suspicious
On 11.12.2017 11:29,
Timo Walther created FLINK-8236:
---
Summary: Allow to set the parallelism of table queries
Key: FLINK-8236
URL: https://issues.apache.org/jira/browse/FLINK-8236
Project: Flink
Issue Type:
Chesnay Schepler created FLINK-8235:
---
Summary: Cannot run spotbugs for single module
Key: FLINK-8235
URL: https://issues.apache.org/jira/browse/FLINK-8235
Project: Flink
Issue Type: Bug
+1 (binding)
- Checked hashes & signatures
- Checked no binaries in source release
- Checked Flink version in Quickstart pom files
Cheers, Fabian
2017-12-11 11:26 GMT+01:00 Stefan Richter :
> +1 (non-binding)
>
> - did extensive cluster tests on Google Cloud with
+1 (non-binding)
- did extensive cluster tests on Google Cloud with special focus on
checkpointing and recovery and Kafka 0.11 end-to-end exactly-once +
at-least-once.
- build from source.
> Am 11.12.2017 um 09:53 schrieb Piotr Nowojski :
>
> Hi,
>
> +1 (non-binding)
Hi,
+1 (non-binding)
I have:
- verified Scala and Java sample projects are creating and working properly and
that Quickstart docs are ok
- verified that ChildFirstClassloader allows user to run his application with
some custom akka version
- tested Kafka 0.11 end to end exactly once
- did some
Till Rohrmann created FLINK-8233:
Summary: Retrieve ExecutionResult by REST polling
Key: FLINK-8233
URL: https://issues.apache.org/jira/browse/FLINK-8233
Project: Flink
Issue Type: Sub-task
Till Rohrmann created FLINK-8232:
Summary: Create RestHandler for long running operations
Key: FLINK-8232
URL: https://issues.apache.org/jira/browse/FLINK-8232
Project: Flink
Issue Type:
Till Rohrmann created FLINK-8231:
Summary: Extend AbstractRestHandler to return response headers
Key: FLINK-8231
URL: https://issues.apache.org/jira/browse/FLINK-8231
Project: Flink
Issue
17 matches
Mail list logo